Date: Sat, 07 Nov 1998 08:32:38 +0100 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: Peter Wemm <peter@netplex.com.au> Cc: Bill Paul <wpaul@skynet.ctr.columbia.edu>, current@FreeBSD.ORG Subject: Re: Grrr... calcru: negative time blah blah blah Message-ID: <10253.910423958@critter.freebsd.dk> In-Reply-To: Your message of "Sat, 07 Nov 1998 12:42:13 %2B0800." <199811070442.MAA18044@spinner.netplex.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <199811070442.MAA18044@spinner.netplex.com.au>, Peter Wemm writes: >> I'm starting to think the problem in this case is an interrupt storm, >> but I'm not sure how to debug it. If I set up a second system to do >> a remote gdb of the first one, can I single step through things like >> interrupt handlers without Weird Things (tm) happening? > >Just a thought that might be worth checking into.. Is the kstack growing >down into struct pstats, the sigacts, and perhaps pcb? This would be >highly dependent on interrupt handlers, machine load (amount of nesting) >etc and could explain why it hits some more than others. Peter, this would probably lead to much more bogosity than what we see here, but you suggestion for a trapdoor under the stack is certainly worthwhile in its own right. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal 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?10253.910423958>