This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug runtime/17140] systemtap.examples/profiling/functioncallcount.stp causing kernel panic on s390x
- From: "dsmith at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Thu, 31 Jul 2014 19:49:18 +0000
- Subject: [Bug runtime/17140] systemtap.examples/profiling/functioncallcount.stp causing kernel panic on s390x
- Auto-submitted: auto-generated
- References: <bug-17140-6586 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17140
--- Comment #3 from David Smith <dsmith at redhat dot com> ---
Here's additional information. The following works fine (using
'kprobe.function'):
# stap -DSTP_ALIBI -ve 'probe kprobe.function("free_pages").call {
printf("here\n") }'
Bug the corresponding 'kernel.function' version crashes almost immediately:
# stap -DSTP_ALIBI -ve 'probe kernel.function("free_pages").call {
printf("here\n") }'
Looking at the translator's C output, 'kernel.function("free_pages").call' puts
probes at 2 addresses:
{ .address=(unsigned long)0x111928ULL, .module="kernel", .section="_stext",
.probe=(&stap_probes[0]), },
{ .address=(unsigned long)0x111910ULL, .module="kernel", .section="_stext",
.probe=(&stap_probes[1]), },
};
Putting a probe at the first address, 0x111928ULL, works fine. Putting a probe
at the 2nd address, 0x111910ULL, causes the BUG to appear immediately.
--
You are receiving this mail because:
You are the assignee for the bug.