This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug runtime/14026] print_ubacktrace doesn't resolve the symbol name
- From: "mjw at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Sun, 06 May 2012 13:09:17 +0000
- Subject: [Bug runtime/14026] print_ubacktrace doesn't resolve the symbol name
- Auto-submitted: auto-generated
- References: <bug-14026-6586@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=14026
--- Comment #18 from Mark Wielaard <mjw at redhat dot com> 2012-05-06 13:09:17 UTC ---
It is strange that the same binary compiled with gcc-4.6 does produce a good
backtrace, while one compiled with gcc-.4.4 doesn't In both cases the FDE
associated with the pc probe point points to a similar CIE.
GCC 4.4 binary:
00003dd4 00000024 00003d98 FDE cie=00000040 pc=08074810..08074863
DW_CFA_advance_loc: 1 to 08074811
[...]
GCC 4.6 binary:
00003d78 0000001c 00003d3c FDE cie=00000040 pc=08075410..08075463
DW_CFA_advance_loc: 4 to 08075414
[...]
In both cases the CIE looks like:
00000040 00000014 00000000 CIE
Version: 1
Augmentation: "zR"
Code alignment factor: 1
Data alignment factor: -4
Return address column: 8
Augmentation data: 1b
DW_CFA_def_cfa: r4 (esp) ofs 4
DW_CFA_offset: r8 (eip) at cfa-4
DW_CFA_nop
DW_CFA_nop
So the result should be the same since the first operand of the FDE is an
DW_CFA_advance_loc that gets you past the probe point pc address (target loc).
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.