Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: James Sampson <i_am_triumph@ofir.dk>
To: GDB Archive <gdb@sources.redhat.com>,
	Tim Combs <tcombs@urbana.css.mot.com>
Subject: RE: Debugging GDB with GDB
Date: Fri, 15 Nov 2002 00:51:00 -0000	[thread overview]
Message-ID: <20021115091559.5966225A8B@postfix2.ofir.com> (raw)

Thanks a lot - I didn't know the ctrl-c options, since I'm pretty new to GDB 
:-D

Now I can get a bit further - More problems are sure to arise ;-)

J.S.


>The .gdbinit file uses "set prompt (top-gdb)" so you can differentiate
>between which gdb is running.  This works best on
>the command line as you can readily see which gdb you are in.  Things
>work the same as when you are debugging a program.  When you want to
>stop use ctrl-c and you will see the top-level prompt and you can step
>through gdb source.  When using the command line, I've always found it
>helpful to open the source file I'm debugging to follow along.
>
>Hope this helps
>Tim



             reply	other threads:[~2002-11-15  8:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-15  0:51 James Sampson [this message]
  -- strict thread matches above, loose matches on Subject: below --
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
2002-11-14  6:13 James Sampson
2002-11-14  6:58 ` Tim Combs
2002-02-01  8:25 Debugging gdb with gdb Salman Khilji
2002-02-01  9:26 ` Daniel Jacobowitz
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

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=20021115091559.5966225A8B@postfix2.ofir.com \
    --to=i_am_triumph@ofir.dk \
    --cc=gdb@sources.redhat.com \
    --cc=tcombs@urbana.css.mot.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