From: Michael Elizabeth Chastain <mec@shout.net>
To: ac131313@redhat.com, gdb@sources.redhat.com
Subject: Re: [Fwd: Unwinding through `no return'?]
Date: Wed, 13 Aug 2003 17:43:00 -0000 [thread overview]
Message-ID: <200308131743.h7DHhRIL009378@duracef.shout.net> (raw)
Three comments, kinda superficial:
Sometimes the caller will be in code with no debug info,
such as library code. RA-1 would be good there.
Look at the case where the operating system delivers a signal and sets
up a sigreturn frame. In that case, a return address on a stack
really does point to the first instruction of a function (__restore
on my red hat linux 8 box). RA-1 would be bad there.
Someone, maybe rth?, mentioned that on some architectures,
the ABI requires a nop instruction after a noreturn call.
If we ask gcc to do something like that in all cases it might
make our job easier.
Michael C
next reply other threads:[~2003-08-13 17:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-13 17:43 Michael Elizabeth Chastain [this message]
2003-08-13 18:45 ` Andrew Cagney
-- strict thread matches above, loose matches on Subject: below --
2003-08-13 17:31 Andrew Cagney
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=200308131743.h7DHhRIL009378@duracef.shout.net \
--to=mec@shout.net \
--cc=ac131313@redhat.com \
--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