From: Daniel Jacobowitz <drow@mvista.com>
To: Salman Khilji <salmankhilji@hotmail.com>
Cc: gdb@sources.redhat.com
Subject: Re: Debugging gdb with gdb
Date: Fri, 01 Feb 2002 09:26:00 -0000 [thread overview]
Message-ID: <20020201122613.A28169@nevyn.them.org> (raw)
In-Reply-To: <F47tuKOaxeTBTcnv57p0000b1ec@hotmail.com>
On Fri, Feb 01, 2002 at 04:25:15PM +0000, Salman Khilji wrote:
> I am running gdb under gdb.
>
> Lets assume gdb starts mygdb. I issue the run command in (gdb) without
> setting any breakpoints anywhere. mygdb comes up and the prompt now says
> (mygdb) instead of (gdb). I want to put a break point somewhere inside the
> mygdb code---not the program that mygdb is going to debug. However if I
> issue the break command, the break point is going to be set in the program
> that (mygdb) is going to debug---not in mygdb itself.
>
> So the question is: How do I temporarily stop the target application in
> gdb---set a break point in the target---then continue? This is useful in
> GUI applications as well.
Hit control-C at the (mygdb) prompt, and it should stop on the parent
GDB.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-02-01 17:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-01 8:25 Salman Khilji
2002-02-01 9:26 ` Daniel Jacobowitz [this message]
2002-02-03 12:29 ` Joel Brobecker
2002-02-04 1:32 ` Christophe PLANAT
2002-02-04 12:24 ` Piet/Pete Delaney
2002-02-04 14:02 ` Kevin Buettner
2002-02-04 15:00 ` Piet/Pete Delaney
2002-02-04 15:13 ` Piet/Pete Delaney
2002-11-14 6:13 Debugging GDB with GDB James Sampson
2002-11-14 6:58 ` Tim Combs
2002-11-15 0:51 James Sampson
2006-08-31 16:17 Rajesh Warange
2006-08-31 16:34 ` Daniel Jacobowitz
2006-08-31 17:43 ` Michael Snyder
2006-08-31 21:24 ` Andreas Schwab
2006-08-31 22:54 ` 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=20020201122613.A28169@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=salmankhilji@hotmail.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