This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug uprobes/6841] New: system-wide utrace syscall tracing script don't respond signal
- From: "mhiramat at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 13 Aug 2008 16:40:20 -0000
- Subject: [Bug uprobes/6841] New: system-wide utrace syscall tracing script don't respond signal
- Reply-to: sourceware-bugzilla at sourceware dot org
below script didn't stop when I sent ^C from terminal or SIGTERM from kill command.
---<suspicious2.stp>---
#! stap
global proc,name
probe process("*").syscall {
proc[pid()] <<< 1
name[pid()] = execname()
}
probe end {
foreach(p+ in proc) {
printf("%s(%d) issues syscall %d times\n",
name[p], p, @sum(proc[p]))
}
}
---
but once I sent ^Z and bg, it could catch the signal.
---<terminal log>
$ stap -vvvv suspicious2.stp
<snip>
stapio:stp_main_loop:290 in main loop
stapio:stp_main_loop:297 nb=4
stapio:init_relayfs:124 initializing relayfs
stapio:init_relayfs:148 attempting to open
/sys/kernel/debug/systemtap/stap_3cb8c5f4cd6b7e714b961ad41f71374b_755/trace0
stapio:init_relayfs:148 attempting to open
/sys/kernel/debug/systemtap/stap_3cb8c5f4cd6b7e714b961ad41f71374b_755/trace1
stapio:init_relayfs:154 ncpus=1, bulkmode = 0
stapio:init_relayfs:204 starting threads
stapio:stp_main_loop:297 nb=12
stapio:stp_main_loop:337 probe_start() returned 0
<<(here I sent ^C and ^Z)
[1]+ Stopped stap -vvvv suspicious2.stp
[mhiramat@kumesen utrace]$ bg
[1]+ stap -vvvv suspicious2.stp &
<<(after bg, it caught
signals)
stapio:signal_thread:33 sigproc 2 (Interrupt)
stapio:stp_main_loop:297 nb=4
stapio:stp_main_loop:330 got STP_EXIT
stapio:cleanup_and_exit:248 detach=0
stapio:close_relayfs:221 closing
auditd(2318) issues syscall 2 times
audispd(2320) issues syscall 1 times
irqbalance(2362) issues syscall 20 times
rpc.idmapd(2448) issues syscall 20 times
pcscd(2549) issues syscall 343 times
setroubleshootd(2579) issues syscall 664 times
automount(2595) issues syscall 27 times
python(2632) issues syscall 3 times
sendmail(2678) issues syscall 15 times
gpm(2699) issues syscall 28 times
avahi-daemon(2876) issues syscall 7 times
gam_server(2900) issues syscall 9 times
hald-addon-stor(2913) issues syscall 28 times
gdm-rh-security(3111) issues syscall 121 times
sshd(3182) issues syscall 137 times
bash(3183) issues syscall 71 times
stapio(4018) issues syscall 68 times
stapio:close_relayfs:240 done
stapio:cleanup_and_exit:261 closing control channel
stapio:cleanup_and_exit:267 removing stap_3cb8c5f4cd6b7e714b961ad41f71374b_755
Pass 5: run completed in 10usr/30sys/8380real ms.
Running rm -rf /tmp/stapZRbjve
--
Summary: system-wide utrace syscall tracing script don't respond
signal
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: uprobes
AssignedTo: systemtap at sources dot redhat dot com
ReportedBy: mhiramat at redhat dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=6841
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.