DTrace: Sending ^C while running script produces no output

[Brandon Gooch]

On Sat, Dec 4, 2010 at 2:32 PM, Andriy Gapon <avg at freebsd.org> wrote:
> on 03/12/2010 07:20 Brandon Gooch said the following:
>> I've been tinkering with DTrace a bit, and I've notice something
>> peculiar on each system I've tried it on.
>>
>> Sending ^C from the keyboard in the terminal (console, XTerm, Konsole)
>> produces no output [1].
>
> Can you ktrace the dtrace process?
> I wonder, could it be that SIGINT from ^C is somehow delivered twice?..

I'll give it a shot in just a bit.

>> For example, while trying out a one-liner (from
>> http://www.brendangregg.com/DTrace/dtrace_oneliners.txt):
>>
>> brandon at d820:~$ sudo dtrace -n 'syscall:::entry { @num[execname] = count(); }'
>> dtrace: description 'syscall:::entry ' matched 514 probes
>> ^C
>
> BTW, sudo might play a role here...  Just a thought.

I could see that for sure. I can't believe I hadn't thought of that
right off the bat, but then again I tested while logged in as root
from the console -- I think :/

Human memory is unreliable y'know...

-Brandon