From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug tapsets/23879] print_ubacktrace can not print function name
Date: Mon, 12 Nov 2018 14:28:00 -0000 [thread overview]
Message-ID: <bug-23879-6586-yswlB412qP@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-23879-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=23879
Frank Ch. Eigler <fche at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fche at redhat dot com
--- Comment #2 from Frank Ch. Eigler <fche at redhat dot com> ---
It depends how the two versions of the target program were compiled. Perhaps
the second one was stripped (including symbol info), so stap (and tools like
gdb) would have no chance to resolve addresses to names. Perhaps the unwind
data was not generated the same way (possibly CFLAGS without
-fasynchronous-unwind-tables?).
A comparison with "readelf -S" between the two binaries could help clear this
up.
Also, that advice re. rerunning with -DDEBUG_UNWIND is a good one, the data
would help.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2018-11-12 14:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-12 9:52 [Bug tapsets/23879] New: " idealities at gmail dot com
2018-11-12 9:53 ` [Bug tapsets/23879] " idealities at gmail dot com
2018-11-12 14:28 ` fche at redhat dot com [this message]
2018-11-13 1:58 ` idealities at gmail dot com
2018-11-13 5:35 ` idealities at gmail dot com
2019-08-21 14:05 ` fche at redhat dot com
2019-08-22 0:12 ` 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-23879-6586-yswlB412qP@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).