From: James Sampson <i_am_triumph@ofir.dk>
To: GDB Archive <gdb@sources.redhat.com>
Subject: Debugging GDB and breaking?
Date: Wed, 18 Dec 2002 05:49:00 -0000 [thread overview]
Message-ID: <20021218142122.7955367D33@postfix3.ofir.com> (raw)
Hello
I'm debugging the GDB with the GDB - Not to catch a bug, but to investigate
what's going on. In that case I wan't to step through everything the GDB does
when just working with it manualy. Where I am now, I've loaded a file into the
GDB being debugged, and I want the other GDB to take over, so I can see what
happens, when the GDB actually sets a breakpoint in this small testprogram.
But when I type e.g. "break main", the control never goes back to the other
GDB, so I can't see what's going on.
Isn't there a command to issue a breakpoint at the next line of code instead
of a obsolute position (name, address)?
Or could someone tell me where to look in the source code for the functions
which places a breakpoint?.
Best Regards
James
next reply other threads:[~2002-12-18 13:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-18 5:49 James Sampson [this message]
2002-12-18 7:23 Michael Elizabeth Chastain
2002-12-18 7:59 ` Andreas Schwab
2002-12-18 11:01 ` Grant Edwards
2002-12-19 1:16 James Sampson
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=20021218142122.7955367D33@postfix3.ofir.com \
--to=i_am_triumph@ofir.dk \
--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