From: Markus Deuling <deuling@de.ibm.com>
To: GDB Discuss <gdb@sources.redhat.com>
Subject: Re: Debug the Debugger
Date: Wed, 10 Jan 2007 19:58:00 -0000 [thread overview]
Message-ID: <45A54567.8080808@de.ibm.com> (raw)
In-Reply-To: <20070110195443.GA11558@nevyn.them.org>
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 :-)
Thank you both.
Regards,
Markus
--
Markus Deuling
GNU Toolchain for Linux on Cell BE
deuling@de.ibm.com
next prev parent reply other threads:[~2007-01-10 19:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-10 19:47 Markus Deuling
2007-01-10 19:52 ` Paul Koning
2007-01-10 19:54 ` Daniel Jacobowitz
2007-01-10 19:58 ` Markus Deuling [this message]
2007-02-21 21:57 ` Michael Snyder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45A54567.8080808@de.ibm.com \
--to=deuling@de.ibm.com \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox