This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug tapsets/11433] __stp_stack_print() needs uprobes.ko


------- Additional Comments From wenji dot huang at oracle dot com  2010-04-21 09:16 -------
(In reply to comment #0)
> On i386 and x86_64, __stp_stack_print() calls uprobe_get_pc().  If uprobes.ko
> doesn't happen to already be loaded, you'll get "Unknown symbol uprobe_get_pc"
> in pass 5.
> 
> $ stap -e 'probe timer.profile { print_ubacktrace() }'
> Error inserting module
> '/tmp/stapUMosL6/stap_372d2e868930605380a28ec58c3bb989_1157.ko': Unknown symbol
> in module
> Retrying, after attempted removal of module
> stap_372d2e868930605380a28ec58c3bb989_1157 (rc -1)
> Error inserting module
> '/tmp/stapUMosL6/stap_372d2e868930605380a28ec58c3bb989_1157.ko': Unknown symbol
> in module
> Pass 5: run failed.  Try again with another '--vp 00001' option.
> $ dmesg | tail -n1
> stap_372d2e868930605380a28ec58c3bb989_1157: Unknown symbol uprobe_get_pc

This happens on utrace-kernel, but without loaded uprobe module. On non-utrace
kernel, it works well. 
See thread
http://sources.redhat.com/ml/systemtap/2010-q1/msg00370.html

> 
> A possible answer is that print_ubacktrace() is useless outside of uprobes
> probepoints anyway, but I hope we can do better than a pass-5 failure...

Or automatically check uprobe module before loading stap module once
print_ubacktrace() is called.


-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=11433

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]