Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Fernando Nasser <fnasser@cygnus.com>
Cc: Michael Snyder <msnyder@cygnus.com>, gdb-patches@sources.redhat.com
Subject: Re: [PATCH RFA] ending-run.exp
Date: Mon, 09 Jul 2001 13:47:00 -0000	[thread overview]
Message-ID: <3B4A1873.9000302@cygnus.com> (raw)
In-Reply-To: <3B4A132E.AA2DE377@cygnus.com>

> Well, main() is normally called from inside crt0  from some sort of "start" function.  When you step past the return from main you should return to the frame above main, i.e., to after the call to main inside the "start" function in crt0.
> 
> If it is not stopping there it is either a bug or some new situation that did not use to exist.
> 
> I don't think we should accept "Program exited normally" until we understand a little bit more of what is actually happening when we get this message.


Ulgh, that problem.  At present GDB's behavour is poorly define 

for when it comes to what to do with the bottom (outer most) stack 
frames. For instance backtrace code sometimes includes _start but 
sometimes does not.

There needs to be a consistent story as to what is reasonable.  With 
that in mind I can image a GDB that does something like:

	(gdb)
	4: return 0;
	(gdb) list
	main ()
	{
	  printf ("Hello World\n");
	  return 0;
	}
	(gdb) step
	File has no symbols, single stepping until exit
	Program exited normally.
	(gdb)

	Andrew






  parent reply	other threads:[~2001-07-09 13:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-02 14:43 Michael Snyder
     [not found] ` <3B4A132E.AA2DE377@cygnus.com>
2001-07-09 13:47   ` Andrew Cagney [this message]
2001-07-12 17:09   ` Michael Snyder
2001-07-13 12:47     ` Fernando Nasser
2001-07-25 15:42       ` Michael Snyder
2001-07-02 15:18 Michael Elizabeth Chastain

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=3B4A1873.9000302@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=fnasser@cygnus.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=msnyder@cygnus.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