Date: Wed, 3 Jan 2001 15:04:52 +1030 From: Greg Lehey <grog@lemis.com> To: Zhiui Zhang <zzhang@cs.binghamton.edu> Cc: Doug White <dwhite@resnet.uoregon.edu>, freebsd-hackers@FreeBSD.ORG Subject: Re: kernel debugging suggestion needed Message-ID: <20010103150452.F4336@wantadilla.lemis.com> In-Reply-To: <Pine.SOL.4.21.0101022319400.7168-100000@opal>; from zzhang@cs.binghamton.edu on Tue, Jan 02, 2001 at 11:22:49PM -0500 References: <Pine.BSF.4.21.0101021402410.38463-100000@resnet.uoregon.edu> <Pine.SOL.4.21.0101022319400.7168-100000@opal>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday, 2 January 2001 at 23:22:49 -0500, Zhiui Zhang wrote: > On Tue, 2 Jan 2001, Doug White wrote: > >> On Tue, 2 Jan 2001, Zhiui Zhang wrote: >> >>> >>> I have written a KLD and am debugging it. The program often hangs after >>> runs for a while (I guess it enters into some dead loop). Is there a way >>> to attach to the process and somehow find out which code it is executing >>> (with remote debugging or ddb)? >> >> kld debugging is a bit tricky. Take a look at the debugging macros and >> bits that Greg Lehey put together for vinum for a starting point. You have >> to calculate the appropriate offset to get to the KLD code in gdb. > > I already did this. I hope that I can find a way to know which process is > running which part of the KLD code endlessly. There are other macros in my .gdbinits which give you backtraces of other processes. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010103150452.F4336>