Re: remote debugging question

On Tue, 28 Sep 2004 16:22:29 -0700 Jerry Toung <[EMAIL PROTECTED]> wrote: > Hi Greg, > thank you for all the feedback. The "set remotebaud 1" thing in my > previous email was a typo, I usually enter 9600. > So you're saying that I may have a communication problem. I would like > to point out that

Re: remote debugging question

Hi Greg, thank you for all the feedback. The "set remotebaud 1" thing in my previous email was a typo, I usually enter 9600. So you're saying that I may have a communication problem. I would like to point out that I can use "cu -l cuaa0 -s 9600" on both side and all is well. What do you think c

Re: remote debugging question

On Monday, 27 September 2004 at 11:07:21 -0700, Jerry Toung wrote: > Good morning list, > I CAN connect to the target but the 'bt" command return #0 0x in ?? > () at the remote. That suggests that you're not connected. > So this is what I am doing, hopefully somebody can tell me what I a

Re: debugging question

Ah great. Thanks alot! Mark On Wed, Oct 31, 2001 at 01:11:07AM -0800, Julian Elischer wrote: > Mark Santcroos wrote: > > > > 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 mov

Re: debugging question

Mark Santcroos wrote: > > 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? tr PID gives you teh stack of that PID then set

Re: debugging question

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 repo

Re: debugging question

when the system is looping, hit 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 -- y

Re: debugging question

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. R

debugging question

Hi I suspect that there is some endless loop somewhere in my kernel (-CURRENT). I can escape to ddb but a trace ofcourse only goes back to spot where the ddb gets called from the keyboard. How can I see in what piece of the kernel it is looping? (I know about where it is, but not exactly) I ho

debugging question

I received the following from gdb today: #0 0x0 in ?? () #1 0x280a8d22 in svc_getreqset2 () from /usr/lib/libc.so.4 #2 0x280a8c5b in svc_getreqset () from /usr/lib/libc.so.4 #3 0x804c85f in yp_svc_run () #4 0x804cd94 in main () #5 0x8049a09 in _start () Uhm... I didn't think that was possi