On Sunday, 17 September 2000 at 16:29:41 +0200, Michael Reifenberger wrote:
> Hi,
> ...
>> The frames above are what the system went to as the result of your
>> debugger request. I'd also be interested to see the output of the
>> 'icnt' macro (if this is UP machine) or 'icnt1' (if it's SMP), and
>> 'ps' (the macro I promised above).
> (kgdb) icnt
> 1215544* 566* 0 0* 0 0 1 0
> 1555964* 0* 0* 0* 0 0* 22636* 11
> 1 0 0 0 0 0 441031
> imen: 6f0b
> (kgdb) ps
> pid proc addr uid pri ppid pgrp flag stat comm wchan
> 37 c7874a00 c9665000 0 32 6 36 004086 3 tar piperd c9663f20
> 36 c7874bc0 c960a000 0 32 6 36 004006 3 tar FFS node
>c02f4220
> 35 c7874d80 c9607000 0 32 6 35 004006 3 tar inode c1d2fa00
> 6 c7874f40 c9604000 0 32 1 6 004086 3 sh wait c7874f40
> 5 c7875100 c8295000 0 4 0 0 000204 3 syncer syncer c03236e8
> 4 c78752c0 c8293000 0 4 0 0 100204 3 bufdaemon psleep c03072f0
> 3 c7875480 c8291000 0 4 0 0 000204 3 vmdaemon psleep c0317a00
> 2 c7875640 c828f000 0 4 0 0 100204 3 pagedaemon psleep c02f5938
> 21 c7875800 c78d4000 0 1* 0 0 000204 2 irq8: rtc
> 20 c78759c0 c78d2000 0 1* 0 0 000204 2 irq0: clk
> 19 c7875b80 c78b0000 0 7* 0 0 000204 6 irq5: pcm0
> 18 c7875d40 c788e000 0 7* 0 0 000204 6 irq7: ppc0
> 17 c7875f00 c788c000 0 7* 0 0 000204 6 irq12: psm0
> 16 c78760c0 c788a000 0 7* 0 0 000204 2 irq1: atkbd0
> 15 c7876280 c7887000 0 6* 0 0 000204 6 irq6: fdc0
> 14 c7876440 c7885000 0 6* 0 0 000204 6 irq15: ata1
> 13 c7876600 c7883000 0 6* 0 0 000204 2 irq14: ata0
> 12 c78767c0 c7881000 0 4 0 0 000204 3 random rndslp c0322934
> 11 c7876980 c787f000 0 15* 0 0 008204 6 softinterrupt
> 10 c7876b40 c787d000 0 4 0 0 008204 2 idle
> 1 c7876d00 c787b000 0 4 0 1 004284 3 init wait c7876d00
> 0 c0322960 c03c0000 0 4 0 0 000204 3 swapper sched c0322960
> ...
>> handler. At this point, it would be very interesting to see the value
>> of p->p_comm, which is the process name at the end of the ps listing.
>>
>>> (kgdb) proc 35
>>
>> Why are you interested in this process?
> It was one of the tar's which I grabbed by hand (without your ps macro)
> ...
>
> Whats next to show :-)
To quote:
>> At this point, it would be very interesting to see the value of
>> p->p_comm, which is the process name at the end of the ps listing.
You could also show the content of p->p_pid. If you don't have a p
pointer in the frame you're looking at, use ((struct
*proc)gd_curproc)->p_pid and ((struct *proc)gd_curproc)->p_comm. We
need to know what is hanging.
I'm probably going on holiday for the rest of the week; somebody else
should pick this one up.
Greg
--
Finger [EMAIL PROTECTED] for PGP public key
See complete headers for address and phone numbers
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
