From: Konstantin Karganov <kostik@ispras.ru>
To: "Nathan J. Williams" <nathanw@wasabisystems.com>
Cc: Daniel Jacobowitz <drow@false.org>, <gdb@sources.redhat.com>
Subject: Re: GDB is stepping past main()
Date: Wed, 13 Jul 2005 13:47:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0507131726030.6056-100000@ispserv.ispras.ru> (raw)
In-Reply-To: <mtuirzeesg6.fsf@scrubbing-bubbles.mit.edu>
> You might find the "stepi" command better suits your needs, though I'm
> not at all sure from your messages what, exactly, you think is
> supposed to happen.
I suppose that the program execution starts when main() starts and ends
when main() ends (though in c++ it is not exactly so).
And thus I suppose the debugging to start at the main() beginning and stop
when main() finishes.
The code above main do not exist for me.
Stepping past the end of main should report the program exit.
Best regards,
Konstantin.
next prev parent reply other threads:[~2005-07-13 13:47 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
2005-07-13 13:39 ` Nathan J. Williams
2005-07-13 13:47 ` Konstantin Karganov [this message]
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.0507131726030.6056-100000@ispserv.ispras.ru \
--to=kostik@ispras.ru \
--cc=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=nathanw@wasabisystems.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).