This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug runtime/17181] New: systemtap has problems attaching to resumed processes
- From: "dsmith at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Fri, 18 Jul 2014 19:31:28 +0000
- Subject: [Bug runtime/17181] New: systemtap has problems attaching to resumed processes
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=17181
Bug ID: 17181
Summary: systemtap has problems attaching to resumed processes
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: runtime
Assignee: systemtap at sourceware dot org
Reporter: dsmith at redhat dot com
Systemtap will error when attempting to attach to a resumed process. This
happens with "fake" utrace (seen on RHEL7 and f20).
====
# stap -v -e 'probe syscall.getpid { printf("%s\n", probefunc()) }'
<snip>
Pass 5: starting run.
sys_getpid
<snip>
ERROR: utrace_set_events returned error -114 on pid 1903
WARNING: /usr/bin/staprun exited with status: 1
Pass 5: run completed in 0usr/70sys/8196real ms.
Pass 5: run failed. [man error::pass5]
====
Here's how to reproduce this one:
1. Compile the following C code to 'a.out'.
====
#include <unistd.h>
#include <signal.h>
void main()
{
kill(getpid(), SIGSTOP);
getpid();
}
====
2. Run 'a.out' in the background.
# ./a.out &
[1] <pid>
3. Execute stap command in another console.
# stap -v -e 'probe syscall.getpid { printf("%s\n", probefunc()) }'
4. Resume the stopped process
# kill -cont <pid>
Sometimes the stopped process can get stuck in the 't' state till
kill -9'd.
--
You are receiving this mail because:
You are the assignee for the bug.