[Bug runtime/6646] SystemTap scripts fail with an Oops on x86
wenji dot huang at oracle dot com
sourceware-bugzilla@sourceware.org
Wed Jun 18 16:23:00 GMT 2008
------- Additional Comments From wenji dot huang at oracle dot com 2008-06-18 07:22 -------
To reproduce the problem, just make a little kernel config change and compile
it again.
Then execute any stap script, it will fail in _stp_transport_init (kernel oops).
Both _stp_kallsyms_lookup_name and _stp_init_kernel_symbols depend on
_stp_kernel_symbols which is from debuginfo file or /proc/kallsyms. I believe
runtime facility such as transport shouldn't trust debuginfo too much . The
incorrect debuginfo would result in kprobe register/trigger error, not earlier
stp_transport_init.
The origin code about retrieving kernel symbols is to read /sys/modules/ which
looks like safer although not very graceful.
--
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.
More information about the Systemtap
mailing list