[Bug tapsets/25290] process(EXE).begin may occasionally miss already-running target processes from EXE

agentzh at gmail dot com sourceware-bugzilla@sourceware.org
Thu Dec 19 21:25:00 GMT 2019


https://sourceware.org/bugzilla/show_bug.cgi?id=25290

--- Comment #1 from agentzh <agentzh at gmail dot com> ---
OK, this can be reproduced by a much simpler stap script (a simple one-liner):

    $ stap -m test -p4 -e 'probe process("/home/agentzh/a.out").begin {
println("Hit"); exit() } probe begin { println("Start tracing") }'

    $ while true; do sudo staprun test.ko; sleep 0.1; done

The second command would hang forever upon a "Start tracing" output line (when
./a.out is always running in another terminal).

And /home/agentzh/a.out is generated from exactly the same a.c source file
provided in my previous comment.

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the Systemtap mailing list