This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [RFA, doc RFA] Don't install gdb.PYTHONDIR if -nx


On Mon, Dec 6, 2010 at 1:16 PM, Doug Evans <dje@google.com> wrote:
> On Mon, Dec 6, 2010 at 1:15 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>>> Date: Mon, 6 Dec 2010 12:58:27 -0800
>>> From: Doug Evans <dje@google.com>
>>> Cc: jan.kratochvil@redhat.com, gdb-patches@sourceware.org
>>>
>>> This is mostly just for testing, so I punted.
>>
>> If it's only for testing, do we need to document it in the manual? ?Or
>> maybe just say "for testing GDB using its test suite", and be done.
>
> Well, there's a difference b/w "mostly" and "only". :-)
>
> But I think a ref to node Data Files should be sufficient.
> Whaddayathink?

Without including all of the rest of the patch, which doesn't change,
how about this?

Index: doc/gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.778
diff -u -p -r1.778 gdb.texinfo
--- doc/gdb.texinfo     29 Nov 2010 23:20:57 -0000      1.778
+++ doc/gdb.texinfo     6 Dec 2010 22:13:50 -0000
@@ -1111,6 +1111,12 @@ used if possible.
 Run @value{GDBN} using @var{directory} as its working directory,
 instead of the current directory.

+@item -data-directory @var{directory}
+@cindex @code{--data-directory}
+Run @value{GDBN} using @var{directory} as its data-directory.
+The data-directory is where @value{GDBN} searches for its
+auxiliary files.  @xref{Data Files}.
+
 @item -fullname
 @itemx -f
 @cindex @code{--fullname}


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]