Re: debugging question

2001-10-31 Thread Mark Santcroos

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 move the context of a certain process
> > and trace from there?
> 
> tr PID
> gives you teh stack of that PID
> 
> then set a breakpoint in a location that you know it will go through
> (e.g. one of the return addresses given in the trace) and then 
> continue.
> 
> > 
> > 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 
> > > 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
> 
> -- 
> ++   __ _  __
> |   __--_|\  Julian Elischer |   \ U \/ / hard at work in 
> |  /   \ [EMAIL PROTECTED] +-->x   USA\ a very strange
> | (   OZ)\___   ___ | country !
> +- X_.---._/presently in San Francisco   \_/   \\
>   v
> 
> 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



Re: debugging question

2001-10-31 Thread Julian Elischer

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 a breakpoint in a location that you know it will go through
(e.g. one of the return addresses given in the trace) and then 
continue.

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

-- 
++   __ _  __
|   __--_|\  Julian Elischer |   \ U \/ / hard at work in 
|  /   \ [EMAIL PROTECTED] +-->x   USA\ a very strange
| (   OZ)\___   ___ | country !
+- X_.---._/presently in San Francisco   \_/   \\
  v

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: debugging question

2001-10-30 Thread Mark Santcroos

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



Re: debugging question

2001-10-30 Thread Julian Elischer

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



Re: debugging question

2001-10-30 Thread Andrew R. Reiter

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