search

dtrace4linux / linux

dtrace for linux - kernel driver and userland tools
http://crtags.blogspot.com
1.17k stars 226 forks source link

dtrace -n syscall::execve:entry just hangs #90

Open megele opened 10 years ago

megele commented 10 years ago

compiling dtrace4linux with up-to-date Debian testing(i.e., Jessie), the above dtrace command just hangs indefinitely (i.e., terminated it after 15 minutes).

Similarly

dtrace -P syscall

states that there are 1,300 probes provided by the syscall provider and then continues to list many thousands (if not millions) of probes.

I'll gladly provide debug information if you let me know what would be helpful.

dtrace4linux commented 10 years ago

during the hang, is the cpu being used at all? what does "dmesg" output show? what does /proc/dtrace/trace show?

what is : uname -r

thanks

On 26 November 2014 at 01:57, megele notifications@github.com wrote:

compiling dtrace4linux with up-to-date Debian testing(i.e., Jessie), the above dtrace command just hangs indefinitely (i.e., terminated it after 15 minutes).

Similarly dtrace -P syscall

states that there are 1,300 probes provided by the syscall provider and then continues to list many thousands (if not millions) of probes.

I'll gladly provide debug information if you let me know what would be helpful.

— Reply to this email directly or view it on GitHub https://github.com/dtrace4linux/linux/issues/90.

megele commented 10 years ago

Hi,

sorry for the delay.

No the CPU is not consumed by the dtrace process. The contents of /proc/dtrace/trace is here: http://pastebin.com/2i9LBPPb And strace -p ) shows that it's constantly waiting for a futex (see here: http://pastebin.com/8LWfnpvw).

uname -r 3.16.0-4-amd64

dtrace4linux commented 10 years ago

i set up a jessie system and can reproduce this along with clone() core dumping the invoking app.

look for an update in a few days.

On 30 November 2014 at 03:28, megele notifications@github.com wrote:

Hi,

sorry for the delay.

No the CPU is not consumed by the dtrace process. The contents of /proc/dtrace/trace is here: http://pastebin.com/2i9LBPPb And strace -p ) shows that it's constantly waiting for a futex (see here: http://pastebin.com/8LWfnpvw).

uname -r 3.16.0-4-amd64

— Reply to this email directly or view it on GitHub https://github.com/dtrace4linux/linux/issues/90#issuecomment-64974241.