Re: kernel backtrace of sleeping processes

2002-04-22 Thread Ian Dowse
In message <[EMAIL PROTECTED]>, Robe rt Watson writes: >Sigh. Remote gdb, not ddb. I tried the usual tricks (updating $sp in >gdb, etc) but gdb persisted in using the old frame. Nevermind. It seemed In gdb, the "proc" command switches processes, so this should work: proc bt

Re: kernel backtrace of sleeping processes

2002-04-21 Thread Robert Watson
On Sun, 21 Apr 2002, Robert Watson wrote: > On Mon, 22 Apr 2002, Joshua Goodall wrote: > > In recent -CURRENT, you can just use > > trace > > or > > trace > > I have to say that since that since this feature was introduced, life > has become a *lot* easier :-). Sigh. Remote gdb, no

Re: kernel backtrace of sleeping processes

2002-04-21 Thread Robert Watson
On Mon, 22 Apr 2002, Joshua Goodall wrote: > In a remote kgdb, I have struct proc * for several processes that > are sleeping and I want the kernel backtraces for them. To illustrate: > > (kgdb) set var $p201 = allproc.lh_first->p_list.le_next->p_list.le_next > (kgdb) print $p201->p_pid > $12 =

kernel backtrace of sleeping processes

2002-04-21 Thread Joshua Goodall
In a remote kgdb, I have struct proc * for several processes that are sleeping and I want the kernel backtraces for them. To illustrate: (kgdb) set var $p201 = allproc.lh_first->p_list.le_next->p_list.le_next (kgdb) print $p201->p_pid $12 = 201 (kgdb) print $p201->p_xxthread.td_wmesg $13 = 0xc024