This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug runtime/6646] SystemTap scripts fail with an Oops on x86
- From: "ananth at in dot ibm dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 19 Jun 2008 03:07:09 -0000
- Subject: [Bug runtime/6646] SystemTap scripts fail with an Oops on x86
- References: <20080616053045.6646.ananth@in.ibm.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From ananth at in dot ibm dot com 2008-06-19 03:07 -------
Re: comment #13, with --ignore-dwarf --ignore-vmlinux --kmap=/proc/kallsyms, the
script is able to resolve the probe address correctly, but it still crashes 'cos
of the incorrect modules_op address.
[ananth@jataayu ~]$ stap -vv -k --ignore-dwarf --ignore-vmlinux
--kmap=/proc/kallsyms current-parent.stp
...
Pass 1: parsed user script and 42 library script(s) in 600usr/10sys/628real ms.
probe sys_open@?:-1 kernel pc=0xc04678b0
Pass 2: analyzed script: 1 probe(s), 3 function(s), 1 embed(s), 0 global(s) in
90usr/70sys/1902real ms.
probe_1365 locks nothing
dwfl_module_getsym: name is modules_op, st_value is c11d1580
Re comment #14, I don't understand that. We don't see the problem with distro
shipped kernels: a printf in dwfl_module_getsym() shows st_value has the correct
(relocated?) address => runtime already gets the correct address from libdwfl;
in the failing case, this is the 'unrelocated' address shown above.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=6646
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.