kgdb supposedly supports a "cpu N" command where the various CPUs can be
selected.
However when debugging a vmcore file, all CPUs show the same backtrace in
the kernel.

(kgdb) cpu 0
initial pcb at 34d920
#0  dumpsys () at /usr/src/sys/kern/kern_shutdown.c:493
493     in /usr/src/sys/kern/kern_shutdown.c
(kgdb) cpu 1
initial pcb at 34d920
#0  dumpsys () at /usr/src/sys/kern/kern_shutdown.c:493
493     in /usr/src/sys/kern/kern_shutdown.c

The backtraces are identical, a panic occuring from interrupt context. (I
won't bore you with them.)
This is a slightly modified version of 4.7, i386.

The questions:
1. Is this expected kgdb behaviour?  
2. Is there some other way to examine what each CPU was doing?
3. At a panic, are all CPUs not running in the kernel suspended?

Thanks,
David Dolson ([EMAIL PROTECTED], www.sandvine.com)


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

Reply via email to