Date: Wed, 23 Jun 1999 15:54:11 -0700 (PDT) From: Doug <Doug@gorean.org> To: freebsd-current@freebsd.org Subject: Re: ktrace causes kernel panic Message-ID: <Pine.BSF.4.05.9906231549380.8580-100000@dt054n86.san.rr.com> In-Reply-To: <Pine.BSF.4.05.9906231136570.5710-100000@dt054n86.san.rr.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 23 Jun 1999, Doug wrote:
> Using a recent (few days) -current I had a process lock up on me
> last night, so I did a 'ktrace -p whateverthepidwas' and let it run for a
> while. When I issued a 'ktrace -C' in another screen, everything froze and
> the kernel panic'ed. I dropped to the debugger on the console and it was
> definintely ktrace that caused the panic.
To add excitement to this, I worked on it for a while (in part
because I still need to ktrace this process, and in part because I wanted
to see if I could reproduce the crash) and ktrace is not performing the
way I remember it. The last time I used ktrace (which was about a year
ago) all I had to do was 'ktrace -p pid#' and it would attach to that
process, and not let go till I killed it, or the process died. In my
current attempt at it, each time I do the ktrace command it dumps about
1.8M worth of ktrace.out, then ktrace exits, even though the process is
still alive and kicking. I don't see anything that I might be missing from
the man page, so any insight would be appreciated. Otherwise I will call
this a bug and send a PR.
Thanks,
Doug
--
On account of being a democracy and run by the people, we are the only
nation in the world that has to keep a government four years, no matter
what it does.
-- Will Rogers
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.9906231549380.8580-100000>