This is the mail archive of the
mailing list for the GDB project.
Re: Debug the Debugger
- From: Michael Snyder <Michael dot Snyder at palmsource dot com>
- To: Markus Deuling <deuling at de dot ibm dot com>
- Cc: GDB Discuss <gdb at sources dot redhat dot com>
- Date: Wed, 21 Feb 2007 11:58:09 -0800
- Subject: Re: Debug the Debugger
- References: <45A542CC.email@example.com> <20070110195443.GA11558@nevyn.them.org> <45A54567.firstname.lastname@example.org>
On Wed, 2007-01-10 at 20:58 +0100, Markus Deuling wrote:
> Daniel Jacobowitz schrieb:
> > On Wed, Jan 10, 2007 at 08:47:24PM +0100, Markus Deuling wrote:
> >> Hi,
> >> I try debugging gdb with gdb. GDB Internals Manual (19.2, p.96) says "The
> >> info command, when executed without a subcommand in a GDB being debugged by
> >> gdb, will pop you backup to the top leve gdb."
> >> But it doesn't :-(
> > This relies on a breakpoint on info_command. The gdbinit file in the
> > gdb object directory sets that up. If you run GDB from anywhere else,
> > you won't get it.
> > Like Paul, I usually use C-c.
> Aha ?!? Ok, interesting idea. Well, I think I'll take the C-c :-)
And in case that doesn't work, I habitually set a breakpoint on
"help_command". Then you just say "help foo", and you're back in
the top-level debugger.