From: "idealities at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug tapsets/23879] print_ubacktrace can not print function name
Date: Tue, 13 Nov 2018 05:35:00 -0000 [thread overview]
Message-ID: <bug-23879-6586-wWeGeGvoZe@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-23879-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=23879
--- Comment #4 from Shang Yuanchun <idealities at gmail dot com> ---
I find out which really matters is the version of compiler (maybe different
version of gcc turn on different default options or enable new default
functions) and the executable file it generate.
Because if I compile a program on another host with gcc 6.3.0, and copy it to
current host and running stap again, print_ubacktrace() works as expected.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2018-11-13 5:35 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
2018-11-13 1:58 ` idealities at gmail dot com
2018-11-13 5:35 ` idealities at gmail dot com [this message]
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-wWeGeGvoZe@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).