This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug runtime/11573] New: uprobe_get_pc, sayonara
- From: "fche at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 5 May 2010 23:57:28 -0000
- Subject: [Bug runtime/11573] New: uprobe_get_pc, sayonara
- Reply-to: sourceware-bugzilla at sourceware dot org
A systemtap script that uses ubacktrace()-related functions will end
up making a linking reference to the uprobe_get_pc() function. But
if the script does not contain any uprobes, staprun does not load
uprobes.ko so that this reference can be satisfied, and we end up
with silly stuff like:
# rmmod uprobes
# stap -e 'probe begin {print_ubacktrace()}'
WARNING: "uprobe_get_pc"
[/tmp/stapOL691o/stap_c35e2bc620f14ccdee99bf8fb34d2ffd_1192.ko] undefined!
Error inserting module
'/tmp/stapOL691o/stap_c35e2bc620f14ccdee99bf8fb34d2ffd_1192.ko': Unknown symbol
in module
Retrying, after attempted removal of module
stap_c35e2bc620f14ccdee99bf8fb34d2ffd_1192 (rc -1)
Error inserting module
'/tmp/stapOL691o/stap_c35e2bc620f14ccdee99bf8fb34d2ffd_1192.ko': Unknown symbol
in module
Pass 5: run failed. Try again with another '--vp 00001' option.
Possible solutions:
1) kill our reliance on uprobe_get_pc()
2) find a way of informing the translator & staprun that ubacktrace() should
be treated as if a uprobe-y probe was requested - i.e., compile and load
uprobes.ko
3) provide a weak definition of uprobe_get_pc()
--
Summary: uprobe_get_pc, sayonara
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: runtime
AssignedTo: systemtap at sources dot redhat dot com
ReportedBy: fche at redhat dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=11573
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.