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
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)?
Thanks for your help.
-Zhihui
To
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)?
[Sorry for lack of message in this reply but I accidently rm'd the
original emails to reply to :-) ]
One thing I've done in the past is if it's convenient in a section of code
to hijack a function pointer in the kernel, then hijack it so that it will
call your code...
Silly, and not always
On Tuesday, 2 January 2001 at 14:03:16 -0800, 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
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
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
7 matches
Mail list logo
