Date: Tue, 25 Feb 2003 08:50:26 -0500 From: Dave Dolson <ddolson@sandvine.com> To: "'questions@freebsd.org'" <questions@freebsd.org> Subject: kgdb and cpu number question Message-ID: <FE045D4D9F7AED4CBFF1B3B813C853370191877F@mail.sandvine.com>
next in thread | raw e-mail | index | archive | help
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 (ddolson@sandvine.com, www.sandvine.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?FE045D4D9F7AED4CBFF1B3B813C853370191877F>