From: Konstantin Karganov <kostik@ispras.ru>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sources.redhat.com
Subject: Re: GDB is stepping past main()
Date: Wed, 13 Jul 2005 13:31:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0507131654350.6056-100000@ispserv.ispras.ru> (raw)
In-Reply-To: <20050713130541.GA1992@nevyn.them.org>
> Because the user (in your example) has asked it to step out of main.
I asked to step and started waiting for the program termination message.
And get that stopped somewhere "don't know where"...
> If you want to handle this in a debugger, try detecting when you're in
> main, step, are no longer in main, and main is no longer in the
> backtrace.
Don't you think all this detecting is a debugger's task???
Or else it turns out that the "step" in gdb is broken and has no
defined semantics and needs to be carefully controlled from outside
(whether it made the stepping or not and where it happened to stop)!
And all this "detecting" and outside patches-workarounds are very ugly
solution :(
Working with GDB MI itself is finding the way in the dark, and such
"surprises" like broken commands doesn't rise gdb in users eyes at all...
Best regards,
Konstantin.
next prev parent reply other threads:[~2005-07-13 13:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-11 16:21 Thread backtrace termination Jonathan Larmour
2005-07-11 16:23 ` Daniel Jacobowitz
2005-07-11 17:52 ` Jonathan Larmour
2005-07-11 18:19 ` Daniel Jacobowitz
2005-07-12 18:32 ` Jonathan Larmour
2005-07-13 10:35 ` Steven Johnson
2005-07-13 12:53 ` GDB is stepping past main() Konstantin Karganov
2005-07-13 13:05 ` Daniel Jacobowitz
2005-07-13 13:31 ` Konstantin Karganov [this message]
2005-07-13 13:39 ` Nathan J. Williams
2005-07-13 13:47 ` Konstantin Karganov
2005-07-13 13:50 ` Dave Korn
2005-07-13 13:46 ` Daniel Jacobowitz
2005-07-13 13:57 ` Konstantin Karganov
2005-07-14 14:27 ` MI *stopped reason Konstantin Karganov
2005-07-14 14:40 ` Bob Rossi
2005-07-14 15:15 ` Incorrect breakpoint diagnostics in MI Konstantin Karganov
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=Pine.LNX.4.44.0507131654350.6056-100000@ispserv.ispras.ru \
--to=kostik@ispras.ru \
--cc=drow@false.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).