This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug runtime/6764] New: Execution of probefunc.exp causes system hang on s390 system
- From: "srinivasa at in dot ibm dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 24 Jul 2008 10:25:22 -0000
- Subject: [Bug runtime/6764] New: Execution of probefunc.exp causes system hang on s390 system
- Reply-to: sourceware-bugzilla at sourceware dot org
Environment: Kernel-2.6.26-rc9,elfutils-0.131,systemtap-0.7
Execution of probefunc.exp causes system hang on s390. I have narrowed down this
problem, it looks like probing scheduler_tick() along with printing value of
pp() or probefunc() hangs the system.
global funcname;
global funcname1;
probe kernel.statement(0x000000000003b83c).absolute {
funcname = probefunc();
funcname1 = pp();
printf("========%s \n",funcname);
printf("========%s \n",funcname1);
}
probe begin {
printf(" loading \n");
}
probe end {
printf(" unloading \n");
}
However a simple script which probes scheduler_tick() and logs some message
works well on the same system.
probe kernel.statement(0x000000000003b83c).absolute {
printf("hi \n");
}
probe begin {
printf(" loading \n");
}
probe end {
printf(" unloading \n");
}
Could somebody throw light on why printing pp() or probefunc() inside
scheduler_tick() causes system hang.
Thanks in advance
Srinivasa DS
--
Summary: Execution of probefunc.exp causes system hang on s390
system
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: runtime
AssignedTo: systemtap at sources dot redhat dot com
ReportedBy: srinivasa at in dot ibm dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=6764
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.