Date: Sat, 4 Dec 2010 15:27:21 -0600 From: Brandon Gooch <jamesbrandongooch@gmail.com> To: Andriy Gapon <avg@freebsd.org> Cc: freebsd-hackers@freebsd.org Subject: Re: DTrace: Sending ^C while running script produces no output Message-ID: <AANLkTimJJjF2vGQZmyYUOg6r41q2q7nw59dSTOB0M5iv@mail.gmail.com> In-Reply-To: <4CFAA579.1010701@freebsd.org> References: <AANLkTikmxpRQY_nOD6SB32-nd7YTTgysv2zWgzv7ozYy@mail.gmail.com> <4CFAA579.1010701@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Dec 4, 2010 at 2:32 PM, Andriy Gapon <avg@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@d820:~$ sudo dtrace -n 'syscall:::entry { @num[execname] =3D cou= nt(); }' >> dtrace: description 'syscall:::entry ' matched 514 probes >> ^C > > BTW, sudo might play a role here... =A0Just 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTimJJjF2vGQZmyYUOg6r41q2q7nw59dSTOB0M5iv>