[patch, doc RFA] New command-line option -na.
Eli Zaretskii
eliz@gnu.org
Wed Dec 15 06:58:00 GMT 2010
> Date: Tue, 14 Dec 2010 22:25:52 -0800
> From: Doug Evans <dje@google.com>
> Cc: jan.kratochvil@redhat.com, gdb-patches@sourceware.org
>
> On Tue, Dec 14, 2010 at 10:05 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> > "Startup" is not well defined, from the user's POV. Â The manual uses
> > that term loosely as something vaguely understandable by everyone.
> > Wearing my user's hat, when I type "gdb core" or "gdb -p 1234",
> > everything GDB does before I get my first prompt is "startup". Â That
> > includes loading shared libraries (unless auto-solib-add is OFF),
> > AFAIK.
>
> Actually, give it a try.
>
> $ gdb hello
> (gdb) info shared
> No shared libraries loaded at this time.
> (gdb)
What about "gdb core" or "gdb -p PID"? These are the 2 use-cases I
mentioned that involve loading the shared libraries. I know that "gdb
hello" doesn't do that until you actually run the inferior.
> > Â If the command line specified a program to debug, or a process to
> > Â attach to, or a core file, @value{GDBN} loads any auto-loaded
> > Â scripts provided for the program or for its loaded shared libraries.
> > Â @xref{Auto-Loading}.
>
> Works for me, but I'll take out "or for its loaded shared libraries". Ok?
Let's not decide until we are done discussing the above two use-cases.
> The option is only applicable to Python scripts today, so
> why not leave it where it is?
> We can always move it later.
> But I'll go with mentioning python in the command's text.
That's fine with me, as I wrote.
Thanks.
More information about the Gdb-patches
mailing list