Thats what I already said in my email :)
I was hoping that there is some way to dump the codepath of the kernel. Or is it maybe possible from ddb to move the context of a certain process and trace from there? Mark ps. I have narrowed it down already a bit more and hope to come with a bug report on -current in the coming days. On Tue, Oct 30, 2001 at 03:38:45PM -0800, Julian Elischer wrote: > when the system is looping, hit <CTL><ALT><ESC> > to drop into the debugger. > > On Tue, 30 Oct 2001, Andrew R. Reiter wrote: > > > On Tue, 30 Oct 2001, Mark Santcroos wrote: > > > > :How can I see in what piece of the kernel it is looping? > > :(I know about where it is, but not exactly) > > : > > > > Use ddb to set a break -- you may need to do this upon boot (boot -d) > > > > *-------------................................................. > > | Andrew R. Reiter > > | [EMAIL PROTECTED] > > | "It requires a very unusual mind > > | to undertake the analysis of the obvious" -- A.N. Whitehead > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-hackers" in the body of the message > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
