From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/10056] epilogue-area (pre-return) probes
Date: Tue, 11 Dec 2012 20:39:00 -0000 [thread overview]
Message-ID: <bug-10056-6586-NlZqCgUK2x@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-10056-6586@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=10056
--- Comment #3 from Frank Ch. Eigler <fche at redhat dot com> 2012-12-11 20:38:53 UTC ---
It could help to have gcc emit DW_LNS_set_epilogue_begin markers, but there
appears to be no gcc bugzilla entry requesting that. (Plus accessing the return
value at that moment could be tricky as it may not yet reside in the ABI-fixed
value.)
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next parent reply other threads:[~2012-12-11 20:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-10056-6586@http.sourceware.org/bugzilla/>
2012-12-11 20:39 ` fche at redhat dot com [this message]
2013-02-21 18:38 ` jistone at redhat dot com
2009-04-10 17:54 [Bug translator/10056] New: epilogue-area probes fche at redhat dot com
2009-10-16 21:55 ` [Bug translator/10056] epilogue-area (pre-return) probes fche at redhat dot com
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=bug-10056-6586-NlZqCgUK2x@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.org \
/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).