staprun -c deadlocks often

[Frank Ch. Eigler]

Hi, Richard -


rjones wrote:

> systemtap-1.4-9.fc15.x86_64
> kernel 2.6.38.7-30.fc15.x86_64
>
> I'm not sure if I'm "doing it wrong"

Nope, not your fault.

> [...] Here is what I'm doing (as root):
>   stap -p4 \
>   -e 'probe module("ext2").statement ("*@*.c:*") { printf ("%s\n", pp()); }'
> [stap command prints the module name, used below]
>   staprun -o /tmp/stap -c /bin/ls /home/rjones/.systemtap/cache/44/stap_44fe38ee6f62656645948ce5d275d678_260427.ko

Just running stap .... -c /bin/ls should give the same results.  Or
are you cross-compiling?  (If so, there are other methods available
that wouldn't require hand-copying and hand-running staprun.)

> As I say, more often than half the time, instead of printing out a
> directory listing, the staprun command will just hang.  [...]

This sounds like http://sourceware.org/PR10189, where too many warning
messages interfere with non-warning staprun<->module packets.

- FChE