From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/15757] New: on x86_64, 32-bit user backtraces truncated
Date: Fri, 19 Jul 2013 16:16:00 -0000 [thread overview]
Message-ID: <bug-15757-6586@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=15757
Bug ID: 15757
Summary: on x86_64, 32-bit user backtraces truncated
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: runtime
Assignee: systemtap at sourceware dot org
Reporter: dsmith at redhat dot com
On x86_64 RHEL6 (2.6.32-358.6.1.el6.x86_64), there are 296 passes and 80
failures in the systemtap.exelib/exelib.exp testcase. Here are the failures:
====
FAIL:
ustack-uprobesgcc-O3-m32-debug-uprobeslibgcc-O3-m32-debug_uprobeslibgcc-O3-m32-debug
main (0)
FAIL:
ustack-uprobesgcc-O3-m32-debug-uprobeslibgcc-O3-m32-debug_uprobeslibgcc-O3-m32-debug
main_func (2)
FAIL:
ustack-uprobesgcc-O3-m32-debug-uprobeslibgcc-O3-m32-debug_uprobeslibgcc-O3-m32-debug
lib_main (0)
FAIL:
ustack-uprobesgcc-O3-m32-debug-uprobeslibgcc-O3-m32-debug_uprobeslibgcc-O3-m32-debug
lib_func (2)
FAIL:
ustack-uprobesgcc-O3-m32-sep-debug-uprobeslibgcc-O3-m32-debug_uprobeslibgcc-O3-m32-debug
main (0)
FAIL:
ustack-uprobesgcc-O3-m32-sep-debug-uprobeslibgcc-O3-m32-debug_uprobeslibgcc-O3-m32-debug
main_func (2)
FAIL:
ustack-uprobesgcc-O3-m32-sep-debug-uprobeslibgcc-O3-m32-debug_uprobeslibgcc-O3-m32-debug
lib_main (0)
FAIL:
ustack-uprobesgcc-O3-m32-sep-debug-uprobeslibgcc-O3-m32-debug_uprobeslibgcc-O3-m32-debug
lib_func (2)
FAIL:
ustack-uprobesgcc-O3-m32-pie-debug-uprobeslibgcc-O3-m32-debug_uprobeslibgcc-O3-m32-debug
main (0)
FAIL:
ustack-uprobesgcc-O3-m32-pie-debug-uprobeslibgcc-O3-m32-debug_uprobeslibgcc-O3-m32-debug
main_func (2)
FAIL:
ustack-uprobesgcc-O3-m32-pie-debug-uprobeslibgcc-O3-m32-debug_uprobeslibgcc-O3-m32-debug
lib_main (0)
FAIL:
ustack-uprobesgcc-O3-m32-pie-debug-uprobeslibgcc-O3-m32-debug_uprobeslibgcc-O3-m32-debug
lib_func (2)
FAIL:
ustack-uprobesgcc-O3-m32-pie-sep-debug-uprobeslibgcc-O3-m32-debug_uprobeslibgcc-O3-m32-debug
main (0)
FAIL:
ustack-uprobesgcc-O3-m32-pie-sep-debug-uprobeslibgcc-O3-m32-debug_uprobeslibgcc-O3-m32-debug
main_func (2)
FAIL:
ustack-uprobesgcc-O3-m32-pie-sep-debug-uprobeslibgcc-O3-m32-debug_uprobeslibgcc-O3-m32-debug
lib_main (0)
FAIL:
ustack-uprobesgcc-O3-m32-pie-sep-debug-uprobeslibgcc-O3-m32-debug_uprobeslibgcc-O3-m32-debug
lib_func (2)
FAIL:
ustack-uprobesgcc-O3-m32-debug-uprobeslibgcc-O3-m32-sep-debug_uprobeslibgcc-O3-m32-sep-debug
main (0)
FAIL:
ustack-uprobesgcc-O3-m32-debug-uprobeslibgcc-O3-m32-sep-debug_uprobeslibgcc-O3-m32-sep-debug
main_func (2)
FAIL:
ustack-uprobesgcc-O3-m32-debug-uprobeslibgcc-O3-m32-sep-debug_uprobeslibgcc-O3-m32-sep-debug
lib_main (0)
FAIL:
ustack-uprobesgcc-O3-m32-debug-uprobeslibgcc-O3-m32-sep-debug_uprobeslibgcc-O3-m32-sep-debug
lib_func (2)
FAIL:
ustack-uprobesgcc-O3-m32-sep-debug-uprobeslibgcc-O3-m32-sep-debug_uprobeslibgcc-O3-m32-sep-debug
main (0)
FAIL:
ustack-uprobesgcc-O3-m32-sep-debug-uprobeslibgcc-O3-m32-sep-debug_uprobeslibgcc-O3-m32-sep-debug
main_func (2)
FAIL:
ustack-uprobesgcc-O3-m32-sep-debug-uprobeslibgcc-O3-m32-sep-debug_uprobeslibgcc-O3-m32-sep-debug
lib_main (0)
FAIL:
ustack-uprobesgcc-O3-m32-sep-debug-uprobeslibgcc-O3-m32-sep-debug_uprobeslibgcc-O3-m32-sep-debug
lib_func (2)
FAIL:
ustack-uprobesgcc-O3-m32-pie-debug-uprobeslibgcc-O3-m32-sep-debug_uprobeslibgcc-O3-m32-sep-debug
main (0)
FAIL:
ustack-uprobesgcc-O3-m32-pie-debug-uprobeslibgcc-O3-m32-sep-debug_uprobeslibgcc-O3-m32-sep-debug
main_func (2)
FAIL:
ustack-uprobesgcc-O3-m32-pie-debug-uprobeslibgcc-O3-m32-sep-debug_uprobeslibgcc-O3-m32-sep-debug
lib_main (0)
FAIL:
ustack-uprobesgcc-O3-m32-pie-debug-uprobeslibgcc-O3-m32-sep-debug_uprobeslibgcc-O3-m32-sep-debug
lib_func (2)
FAIL:
ustack-uprobesgcc-O3-m32-pie-sep-debug-uprobeslibgcc-O3-m32-sep-debug_uprobeslibgcc-O3-m32-sep-debug
main (0)
FAIL:
ustack-uprobesgcc-O3-m32-pie-sep-debug-uprobeslibgcc-O3-m32-sep-debug_uprobeslibgcc-O3-m32-sep-debug
main_func (2)
FAIL:
ustack-uprobesgcc-O3-m32-pie-sep-debug-uprobeslibgcc-O3-m32-sep-debug_uprobeslibgcc-O3-m32-sep-debug
lib_main (0)
FAIL:
ustack-uprobesgcc-O3-m32-pie-sep-debug-uprobeslibgcc-O3-m32-sep-debug_uprobeslibgcc-O3-m32-sep-debug
lib_func (2)
FAIL:
ustack-uprobesgcc-O3-m32-debug-uprobeslibgcc-O3-m32-prelink-debug_uprobeslibgcc-O3-m32-prelink-debug
main (0)
FAIL:
ustack-uprobesgcc-O3-m32-debug-uprobeslibgcc-O3-m32-prelink-debug_uprobeslibgcc-O3-m32-prelink-debug
main_func (2)
FAIL:
ustack-uprobesgcc-O3-m32-debug-uprobeslibgcc-O3-m32-prelink-debug_uprobeslibgcc-O3-m32-prelink-debug
lib_main (0)
FAIL:
ustack-uprobesgcc-O3-m32-debug-uprobeslibgcc-O3-m32-prelink-debug_uprobeslibgcc-O3-m32-prelink-debug
lib_func (2)
FAIL:
ustack-uprobesgcc-O3-m32-sep-debug-uprobeslibgcc-O3-m32-prelink-debug_uprobeslibgcc-O3-m32-prelink-debug
main (0)
FAIL:
ustack-uprobesgcc-O3-m32-sep-debug-uprobeslibgcc-O3-m32-prelink-debug_uprobeslibgcc-O3-m32-prelink-debug
main_func (2)
FAIL:
ustack-uprobesgcc-O3-m32-sep-debug-uprobeslibgcc-O3-m32-prelink-debug_uprobeslibgcc-O3-m32-prelink-debug
lib_main (0)
FAIL:
ustack-uprobesgcc-O3-m32-sep-debug-uprobeslibgcc-O3-m32-prelink-debug_uprobeslibgcc-O3-m32-prelink-debug
lib_func (2)
FAIL:
ustack-uprobesgcc-O3-m32-pie-debug-uprobeslibgcc-O3-m32-prelink-debug_uprobeslibgcc-O3-m32-prelink-debug
main (0)
FAIL:
ustack-uprobesgcc-O3-m32-pie-debug-uprobeslibgcc-O3-m32-prelink-debug_uprobeslibgcc-O3-m32-prelink-debug
main_func (2)
FAIL:
ustack-uprobesgcc-O3-m32-pie-debug-uprobeslibgcc-O3-m32-prelink-debug_uprobeslibgcc-O3-m32-prelink-debug
lib_main (0)
FAIL:
ustack-uprobesgcc-O3-m32-pie-debug-uprobeslibgcc-O3-m32-prelink-debug_uprobeslibgcc-O3-m32-prelink-debug
lib_func (2)
FAIL:
ustack-uprobesgcc-O3-m32-pie-sep-debug-uprobeslibgcc-O3-m32-prelink-debug_uprobeslibgcc-O3-m32-prelink-debug
main (0)
FAIL:
ustack-uprobesgcc-O3-m32-pie-sep-debug-uprobeslibgcc-O3-m32-prelink-debug_uprobeslibgcc-O3-m32-prelink-debug
main_func (2)
FAIL:
ustack-uprobesgcc-O3-m32-pie-sep-debug-uprobeslibgcc-O3-m32-prelink-debug_uprobeslibgcc-O3-m32-prelink-debug
lib_main (0)
FAIL:
ustack-uprobesgcc-O3-m32-pie-sep-debug-uprobeslibgcc-O3-m32-prelink-debug_uprobeslibgcc-O3-m32-prelink-debug
lib_func (2)
FAIL:
ustack-uprobesgcc-O3-m32-debug-uprobeslibgcc-O3-m32-prelink-sep-debug_uprobeslibgcc-O3-m32-prelink-sep-debug
main (0)
FAIL:
ustack-uprobesgcc-O3-m32-debug-uprobeslibgcc-O3-m32-prelink-sep-debug_uprobeslibgcc-O3-m32-prelink-sep-debug
main_func (2)
FAIL:
ustack-uprobesgcc-O3-m32-debug-uprobeslibgcc-O3-m32-prelink-sep-debug_uprobeslibgcc-O3-m32-prelink-sep-debug
lib_main (0)
FAIL:
ustack-uprobesgcc-O3-m32-debug-uprobeslibgcc-O3-m32-prelink-sep-debug_uprobeslibgcc-O3-m32-prelink-sep-debug
lib_func (2)
FAIL:
ustack-uprobesgcc-O3-m32-sep-debug-uprobeslibgcc-O3-m32-prelink-sep-debug_uprobeslibgcc-O3-m32-prelink-sep-debug
main (0)
FAIL:
ustack-uprobesgcc-O3-m32-sep-debug-uprobeslibgcc-O3-m32-prelink-sep-debug_uprobeslibgcc-O3-m32-prelink-sep-debug
main_func (2)
FAIL:
ustack-uprobesgcc-O3-m32-sep-debug-uprobeslibgcc-O3-m32-prelink-sep-debug_uprobeslibgcc-O3-m32-prelink-sep-debug
lib_main (0)
FAIL:
ustack-uprobesgcc-O3-m32-sep-debug-uprobeslibgcc-O3-m32-prelink-sep-debug_uprobeslibgcc-O3-m32-prelink-sep-debug
lib_func (2)
FAIL:
ustack-uprobesgcc-O3-m32-pie-debug-uprobeslibgcc-O3-m32-prelink-sep-debug_uprobeslibgcc-O3-m32-prelink-sep-debug
main (0)
FAIL:
ustack-uprobesgcc-O3-m32-pie-debug-uprobeslibgcc-O3-m32-prelink-sep-debug_uprobeslibgcc-O3-m32-prelink-sep-debug
main_func (2)
FAIL:
ustack-uprobesgcc-O3-m32-pie-debug-uprobeslibgcc-O3-m32-prelink-sep-debug_uprobeslibgcc-O3-m32-prelink-sep-debug
lib_main (0)
FAIL:
ustack-uprobesgcc-O3-m32-pie-debug-uprobeslibgcc-O3-m32-prelink-sep-debug_uprobeslibgcc-O3-m32-prelink-sep-debug
lib_func (2)
FAIL:
ustack-uprobesgcc-O3-m32-pie-sep-debug-uprobeslibgcc-O3-m32-prelink-sep-debug_uprobeslibgcc-O3-m32-prelink-sep-debug
main (0)
FAIL:
ustack-uprobesgcc-O3-m32-pie-sep-debug-uprobeslibgcc-O3-m32-prelink-sep-debug_uprobeslibgcc-O3-m32-prelink-sep-debug
main_func (2)
FAIL:
ustack-uprobesgcc-O3-m32-pie-sep-debug-uprobeslibgcc-O3-m32-prelink-sep-debug_uprobeslibgcc-O3-m32-prelink-sep-debug
lib_main (0)
FAIL:
ustack-uprobesgcc-O3-m32-pie-sep-debug-uprobeslibgcc-O3-m32-prelink-sep-debug_uprobeslibgcc-O3-m32-prelink-sep-debug
lib_func (2)
FAIL:
ustack-uprobesgcc-O3-m32-debug-uprobeslibgcc-O3-m32-prelink-sep-debug-after_uprobeslibgcc-O3-m32-prelink-sep-debug-after
main (0)
FAIL:
ustack-uprobesgcc-O3-m32-debug-uprobeslibgcc-O3-m32-prelink-sep-debug-after_uprobeslibgcc-O3-m32-prelink-sep-debug-after
main_func (2)
FAIL:
ustack-uprobesgcc-O3-m32-debug-uprobeslibgcc-O3-m32-prelink-sep-debug-after_uprobeslibgcc-O3-m32-prelink-sep-debug-after
lib_main (0)
FAIL:
ustack-uprobesgcc-O3-m32-debug-uprobeslibgcc-O3-m32-prelink-sep-debug-after_uprobeslibgcc-O3-m32-prelink-sep-debug-after
lib_func (2)
FAIL:
ustack-uprobesgcc-O3-m32-sep-debug-uprobeslibgcc-O3-m32-prelink-sep-debug-after_uprobeslibgcc-O3-m32-prelink-sep-debug-after
main (0)
FAIL:
ustack-uprobesgcc-O3-m32-sep-debug-uprobeslibgcc-O3-m32-prelink-sep-debug-after_uprobeslibgcc-O3-m32-prelink-sep-debug-after
main_func (2)
FAIL:
ustack-uprobesgcc-O3-m32-sep-debug-uprobeslibgcc-O3-m32-prelink-sep-debug-after_uprobeslibgcc-O3-m32-prelink-sep-debug-after
lib_main (0)
FAIL:
ustack-uprobesgcc-O3-m32-sep-debug-uprobeslibgcc-O3-m32-prelink-sep-debug-after_uprobeslibgcc-O3-m32-prelink-sep-debug-after
lib_func (2)
FAIL:
ustack-uprobesgcc-O3-m32-pie-debug-uprobeslibgcc-O3-m32-prelink-sep-debug-after_uprobeslibgcc-O3-m32-prelink-sep-debug-after
main (0)
FAIL:
ustack-uprobesgcc-O3-m32-pie-debug-uprobeslibgcc-O3-m32-prelink-sep-debug-after_uprobeslibgcc-O3-m32-prelink-sep-debug-after
main_func (2)
FAIL:
ustack-uprobesgcc-O3-m32-pie-debug-uprobeslibgcc-O3-m32-prelink-sep-debug-after_uprobeslibgcc-O3-m32-prelink-sep-debug-after
lib_main (0)
FAIL:
ustack-uprobesgcc-O3-m32-pie-debug-uprobeslibgcc-O3-m32-prelink-sep-debug-after_uprobeslibgcc-O3-m32-prelink-sep-debug-after
lib_func (2)
FAIL:
ustack-uprobesgcc-O3-m32-pie-sep-debug-uprobeslibgcc-O3-m32-prelink-sep-debug-after_uprobeslibgcc-O3-m32-prelink-sep-debug-after
main (0)
FAIL:
ustack-uprobesgcc-O3-m32-pie-sep-debug-uprobeslibgcc-O3-m32-prelink-sep-debug-after_uprobeslibgcc-O3-m32-prelink-sep-debug-after
main_func (2)
FAIL:
ustack-uprobesgcc-O3-m32-pie-sep-debug-uprobeslibgcc-O3-m32-prelink-sep-debug-after_uprobeslibgcc-O3-m32-prelink-sep-debug-after
lib_main (0)
FAIL:
ustack-uprobesgcc-O3-m32-pie-sep-debug-uprobeslibgcc-O3-m32-prelink-sep-debug-after_uprobeslibgcc-O3-m32-prelink-sep-debug-after
lib_func (2)
====
In reality, there is really only one type of failure being pointed out here,
the fact that 32-on-64-bit executables have short user backtraces. The failures
are magnified because the test executable gets compiled lots of different ways
- different levels of optimization, with/without prelink, etc.
From the systemtap.log file for a 64-bit executable:
====
0x4005f0 : main_func+0x0/0x50
[...suite/uprobesgcc-O3-m64-debug-uprobeslibgcc-O3-m64-debug_exe]
0x400658 : main+0x18/0x30
[...suite/uprobesgcc-O3-m64-debug-uprobeslibgcc-O3-m64-debug_exe]
0x381081ecdd : __libc_start_main+0xfd/0x1d0 [/lib64/libc-2.12.so]
0x400529 : _start+0x29/0x2c
[...suite/uprobesgcc-O3-m64-debug-uprobeslibgcc-O3-m64-debug_exe]
====
Here's the same backtrace, but for a 32-on-64-bit version of that executable:
====
0x80484c0 : main_func+0x0/0x50
[...suite/uprobesgcc-O3-m32-debug-uprobeslibgcc-O3-m32-debug_exe]
====
The test script (in systemtap.exelib/libmarkunamestack.stp) calls
print_ubacktrace().
On x86_64 rawhide (3.11.0-0.rc0.git7.1.fc20.x86_64), this test passes
completely.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2013-07-19 16:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-19 16:16 dsmith at redhat dot com [this message]
2013-07-24 15:12 ` [Bug runtime/15757] " lberk at redhat dot com
2016-05-24 18:56 ` fche at redhat dot com
2017-10-11 10:44 ` mark at klomp dot org
2017-10-11 10:48 ` mjw at fedoraproject dot org
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-15757-6586@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).