* Unknown symbol error using stap in 2.6.31 on ARM
@ 2012-12-30 1:55 Cipher Chen
2012-12-30 9:23 ` Alexander Lochmann
0 siblings, 1 reply; 6+ messages in thread
From: Cipher Chen @ 2012-12-30 1:55 UTC (permalink / raw)
To: systemtap
Hi,
I met the same problem descripted here:
http://sourceware-org.1504.n7.nabble.com/Unknown-symbol-error-using-stap-in-RHEL-5-4-td176251.html
What's different is that it's an ARM target. After i got
ntfs_watching.ko, "staprun ntfs_watching.ko" on that, it told me:
dmesg here:
ntfs_watching: Unknown symbol utrace_control
ntfs_watching: Unknown symbol utrace_barrier
ntfs_watching: Unknown symbol __utrace_engine_release
ntfs_watching: Unknown symbol unregister_uretprobe
ntfs_watching: Unknown symbol register_uprobe
ntfs_watching: Unknown symbol unmap_uretprobe
ntfs_watching: Unknown symbol utrace_attach_task
ntfs_watching: Unknown symbol register_uretprobe
ntfs_watching: Unknown symbol unmap_uprobe
ntfs_watching: Unknown symbol utrace_set_events
ntfs_watching: Unknown symbol unregister_uprobe
So i tried something mentioned in that thread, it didnt work since
it's linux-2.6.31.5 without CONFIG_UPROBES.
It doesnt have any modules running.
Can we say that staprun ran with its own uprobes.ko?
Then I also copied the uprobes.ko in /tmp/stap**** generated on host
to the ARM target, and "insmod uprobes.ko"
dmesg here:
uprobes: Unknown symbol utrace_control
uprobes: Unknown symbol utrace_attach_pid
uprobes: Unknown symbol utrace_set_events
("staprun ntfs_watching -u" told me these too)
Any thoughts on what might be causing this problem?
Thanks!
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: Unknown symbol error using stap in 2.6.31 on ARM 2012-12-30 1:55 Unknown symbol error using stap in 2.6.31 on ARM Cipher Chen @ 2012-12-30 9:23 ` Alexander Lochmann 2012-12-30 12:40 ` Cipher Chen 2012-12-31 12:18 ` Cipher Chen 0 siblings, 2 replies; 6+ messages in thread From: Alexander Lochmann @ 2012-12-30 9:23 UTC (permalink / raw) To: Cipher Chen; +Cc: systemtap Hi, try to run stap with "--compatible=1.8". Stap needs uprobe support for some builtin functions as weel. Using this option it will use old fashion builtin function. Greetings Alex On 12/30/2012 02:55 AM, Cipher Chen wrote: > Hi, > I met the same problem descripted here: > http://sourceware-org.1504.n7.nabble.com/Unknown-symbol-error-using-stap-in-RHEL-5-4-td176251.html > > What's different is that it's an ARM target. After i got > ntfs_watching.ko, "staprun ntfs_watching.ko" on that, it told me: > dmesg here: > ntfs_watching: Unknown symbol utrace_control > ntfs_watching: Unknown symbol utrace_barrier > ntfs_watching: Unknown symbol __utrace_engine_release > ntfs_watching: Unknown symbol unregister_uretprobe > ntfs_watching: Unknown symbol register_uprobe > ntfs_watching: Unknown symbol unmap_uretprobe > ntfs_watching: Unknown symbol utrace_attach_task > ntfs_watching: Unknown symbol register_uretprobe > ntfs_watching: Unknown symbol unmap_uprobe > ntfs_watching: Unknown symbol utrace_set_events > ntfs_watching: Unknown symbol unregister_uprobe > > So i tried something mentioned in that thread, it didnt work since > it's linux-2.6.31.5 without CONFIG_UPROBES. > It doesnt have any modules running. > Can we say that staprun ran with its own uprobes.ko? > > Then I also copied the uprobes.ko in /tmp/stap**** generated on host > to the ARM target, and "insmod uprobes.ko" > dmesg here: > uprobes: Unknown symbol utrace_control > uprobes: Unknown symbol utrace_attach_pid > uprobes: Unknown symbol utrace_set_events > ("staprun ntfs_watching -u" told me these too) > > Any thoughts on what might be causing this problem? > > > > Thanks! ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Unknown symbol error using stap in 2.6.31 on ARM 2012-12-30 9:23 ` Alexander Lochmann @ 2012-12-30 12:40 ` Cipher Chen 2013-01-02 18:44 ` Josh Stone 2012-12-31 12:18 ` Cipher Chen 1 sibling, 1 reply; 6+ messages in thread From: Cipher Chen @ 2012-12-30 12:40 UTC (permalink / raw) To: Alexander Lochmann; +Cc: systemtap Hi, Alexander On Sun, Dec 30, 2012 at 5:23 PM, Alexander Lochmann <alexander.lochmann@tu-dortmund.de> wrote: > Hi, > > try to run stap with "--compatible=1.8". > Stap needs uprobe support for some builtin functions as weel. Using this > option it will use old fashion builtin function. I'm not sure this would help, since I've already tried version 1.8 and snapshot 20122222(?), too(I mean re-install the whole systemtap). And it didn't work either.(current used is 2.0) Anyway, I'll try that again tomorrow. Thanks. > > Greetings > Alex > > > On 12/30/2012 02:55 AM, Cipher Chen wrote: >> >> Hi, >> I met the same problem descripted here: >> >> http://sourceware-org.1504.n7.nabble.com/Unknown-symbol-error-using-stap-in-RHEL-5-4-td176251.html >> >> What's different is that it's an ARM target. After i got >> ntfs_watching.ko, "staprun ntfs_watching.ko" on that, it told me: >> dmesg here: >> ntfs_watching: Unknown symbol utrace_control >> ntfs_watching: Unknown symbol utrace_barrier >> ntfs_watching: Unknown symbol __utrace_engine_release >> ntfs_watching: Unknown symbol unregister_uretprobe >> ntfs_watching: Unknown symbol register_uprobe >> ntfs_watching: Unknown symbol unmap_uretprobe >> ntfs_watching: Unknown symbol utrace_attach_task >> ntfs_watching: Unknown symbol register_uretprobe >> ntfs_watching: Unknown symbol unmap_uprobe >> ntfs_watching: Unknown symbol utrace_set_events >> ntfs_watching: Unknown symbol unregister_uprobe >> >> So i tried something mentioned in that thread, it didnt work since >> it's linux-2.6.31.5 without CONFIG_UPROBES. >> It doesnt have any modules running. >> Can we say that staprun ran with its own uprobes.ko? >> >> Then I also copied the uprobes.ko in /tmp/stap**** generated on host >> to the ARM target, and "insmod uprobes.ko" >> dmesg here: >> uprobes: Unknown symbol utrace_control >> uprobes: Unknown symbol utrace_attach_pid >> uprobes: Unknown symbol utrace_set_events >> ("staprun ntfs_watching -u" told me these too) >> >> Any thoughts on what might be causing this problem? >> >> >> >> Thanks! > > ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Unknown symbol error using stap in 2.6.31 on ARM 2012-12-30 12:40 ` Cipher Chen @ 2013-01-02 18:44 ` Josh Stone 2013-01-03 1:45 ` Cipher Chen 0 siblings, 1 reply; 6+ messages in thread From: Josh Stone @ 2013-01-02 18:44 UTC (permalink / raw) To: Cipher Chen; +Cc: systemtap On 12/30/2012 04:40 AM, Cipher Chen wrote: > On Sun, Dec 30, 2012 at 5:23 PM, Alexander Lochmann wrote: >> try to run stap with "--compatible=1.8". >> Stap needs uprobe support for some builtin functions as weel. Using this >> option it will use old fashion builtin function. > > I'm not sure this would help, since I've already tried version 1.8 > and snapshot 20122222(?), too(I mean re-install the whole systemtap). > And it didn't work either.(current used is 2.0) > Anyway, I'll try that again tomorrow. I gather from the name "ntfs_watching" that you're not actually trying to probe any userspace? In that case, Alex is referring to the probefunc() change, which --compatible=1.8 ought to fix. I also recently added a ppfunc() to git which acts like the old way, parsing the function name out of pp(). In any case, it would help if you shared the script you're using, or at least enough of it that triggers the issue. Thanks, Josh ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Unknown symbol error using stap in 2.6.31 on ARM 2013-01-02 18:44 ` Josh Stone @ 2013-01-03 1:45 ` Cipher Chen 0 siblings, 0 replies; 6+ messages in thread From: Cipher Chen @ 2013-01-03 1:45 UTC (permalink / raw) To: Josh Stone; +Cc: systemtap On Thu, Jan 3, 2013 at 2:44 AM, Josh Stone <jistone@redhat.com> wrote: > On 12/30/2012 04:40 AM, Cipher Chen wrote: >> On Sun, Dec 30, 2012 at 5:23 PM, Alexander Lochmann wrote: >>> try to run stap with "--compatible=1.8". >>> Stap needs uprobe support for some builtin functions as weel. Using this >>> option it will use old fashion builtin function. >> >> I'm not sure this would help, since I've already tried version 1.8 >> and snapshot 20122222(?), too(I mean re-install the whole systemtap). >> And it didn't work either.(current used is 2.0) >> Anyway, I'll try that again tomorrow. > > I gather from the name "ntfs_watching" that you're not actually trying > to probe any userspace? In that case, Alex is referring to the > probefunc() change, which --compatible=1.8 ought to fix. I also > recently added a ppfunc() to git which acts like the old way, parsing > the function name out of pp(). > > In any case, it would help if you shared the script you're using, or at > least enough of it that triggers the issue. > In fact, that wasn't a real utrace patch for ARM. I downloaded utrace.patch for 2.6.31, patched it and wrote some similarly functions for ARM by myself which were needed when building the kernel, since that's a really old kernel. ntfs_watching.stp is a simple script, the only user-space probe would be: probe process("/path/to/ntfsmount/").function("*") { printf("%s\n", probefunc()) } Thanks, Cipher > Thanks, > Josh ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Unknown symbol error using stap in 2.6.31 on ARM 2012-12-30 9:23 ` Alexander Lochmann 2012-12-30 12:40 ` Cipher Chen @ 2012-12-31 12:18 ` Cipher Chen 1 sibling, 0 replies; 6+ messages in thread From: Cipher Chen @ 2012-12-31 12:18 UTC (permalink / raw) To: Alexander Lochmann; +Cc: systemtap hi, Alexander Just as what i mentioned below, it didnt work. On Sun, Dec 30, 2012 at 5:23 PM, Alexander Lochmann <alexander.lochmann@tu-dortmund.de> wrote: > Hi, > > try to run stap with "--compatible=1.8". > Stap needs uprobe support for some builtin functions as weel. Using this > option it will use old fashion builtin function. > > Greetings > Alex > > > On 12/30/2012 02:55 AM, Cipher Chen wrote: >> >> Hi, >> I met the same problem descripted here: >> >> http://sourceware-org.1504.n7.nabble.com/Unknown-symbol-error-using-stap-in-RHEL-5-4-td176251.html >> >> What's different is that it's an ARM target. After i got >> ntfs_watching.ko, "staprun ntfs_watching.ko" on that, it told me: >> dmesg here: >> ntfs_watching: Unknown symbol utrace_control >> ntfs_watching: Unknown symbol utrace_barrier >> ntfs_watching: Unknown symbol __utrace_engine_release >> ntfs_watching: Unknown symbol unregister_uretprobe >> ntfs_watching: Unknown symbol register_uprobe >> ntfs_watching: Unknown symbol unmap_uretprobe >> ntfs_watching: Unknown symbol utrace_attach_task >> ntfs_watching: Unknown symbol register_uretprobe >> ntfs_watching: Unknown symbol unmap_uprobe >> ntfs_watching: Unknown symbol utrace_set_events >> ntfs_watching: Unknown symbol unregister_uprobe >> >> So i tried something mentioned in that thread, it didnt work since >> it's linux-2.6.31.5 without CONFIG_UPROBES. >> It doesnt have any modules running. >> Can we say that staprun ran with its own uprobes.ko? >> >> Then I also copied the uprobes.ko in /tmp/stap**** generated on host >> to the ARM target, and "insmod uprobes.ko" >> dmesg here: >> uprobes: Unknown symbol utrace_control >> uprobes: Unknown symbol utrace_attach_pid >> uprobes: Unknown symbol utrace_set_events >> ("staprun ntfs_watching -u" told me these too) >> >> Any thoughts on what might be causing this problem? >> >> >> >> Thanks! > > ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2013-01-03 1:45 UTC | newest] Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2012-12-30 1:55 Unknown symbol error using stap in 2.6.31 on ARM Cipher Chen 2012-12-30 9:23 ` Alexander Lochmann 2012-12-30 12:40 ` Cipher Chen 2013-01-02 18:44 ` Josh Stone 2013-01-03 1:45 ` Cipher Chen 2012-12-31 12:18 ` Cipher Chen
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).