This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug tapsets/11955] signal tapsets don't match
- From: "mjw at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 29 Aug 2010 12:51:14 -0000
- Subject: [Bug tapsets/11955] signal tapsets don't match
- References: <20100829093708.11955.andi-bz@firstfloor.org>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From mjw at redhat dot com 2010-08-29 12:51 -------
They happen to resolve on my fedora kernel build:
$ stap test.stp
sending SIGBUS to bash
SIGBUS bash, code 0 handler 8096700
sending SIGBUS to bash
Linux version 2.6.33.8-149.fc13.i686 (mockbuild@x86-09.phx2.fedoraproject.org)
(gcc version 4.4.4 20100630 (Red Hat 4.4.4-10) (GCC) ) #1 SMP Tue Aug 17
22:45:56 UTC 2010
A "semantic error: failed to retrieve location attribute for local" is often a
compiler bug. As you can see in your error message there is a DIE for the local
variable, but it is missing the location attribute that describes where (in
memory or through registers) this variable can be found. (Note that the fedora
gcc has the VTA patches from gcc 4.5 backported, which help a lot in describing
location information for inlined code/variables.)
Which compiler was used to build your kernel?
You can get a bit more info about what is known about the local variables by
looking up the dieoffset given in the error message with something like
[eu-]readelf [-N] --debug-dump=info /path/to/vmlinux.debuginfo | less
--
http://sourceware.org/bugzilla/show_bug.cgi?id=11955
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.