Date: Sat, 20 Aug 2005 14:27:55 -0400 From: Kris Kennaway <kris@obsecurity.org> To: Marcel Moolenaar <marcel@xcllnt.net> Cc: marcel@FreeBSD.org, sparc64@FreeBSD.org, Kris Kennaway <kris@obsecurity.org> Subject: Re: kgdb still broken? Message-ID: <20050820182755.GA57524@xor.obsecurity.org> In-Reply-To: <3DBF403C-80AA-46B4-A57B-8B78F033E368@xcllnt.net> References: <20050819171555.GA45748@xor.obsecurity.org> <A4D2B753-A1C2-4686-A656-4DF061AB72A8@xcllnt.net> <20050820025336.GA94049@xor.obsecurity.org> <3DBF403C-80AA-46B4-A57B-8B78F033E368@xcllnt.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--ReaqsoxgOBHFXBhH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Aug 19, 2005 at 11:28:14PM -0700, Marcel Moolenaar wrote: > On Aug 19, 2005, at 7:53 PM, Kris Kennaway wrote: >=20 > >It's not making much sense of the backtrace though: > > > >(kgdb) bt > >#0 doadump () at /usr/src.6/sys/kern/kern_shutdown.c:233 > >#1 0x00000000c006a728 in db_fncall (dummy1=3D0, dummy2=3D0, dummy3=3D11= , =20 > >dummy4=3D0x16e9a41a0 "") > > at /usr/src.6/sys/ddb/db_command.c:486 > >#2 0x00000000c006a434 in db_command (last_cmdp=3D0xc040f940, =20 > >cmd_table=3D0x0, aux_cmd_tablep=3D0xc03c8dc8, > > aux_cmd_tablep_end=3D0xc03c8de0) at /usr/src.6/sys/ddb/=20 > >db_command.c:401 > >#3 0x00000000c006a558 in db_command_loop () at /usr/src.6/sys/ddb/=20 > >db_command.c:452 > >#4 0x00000000c006d0b8 in db_trap (type=3D1855603632, code=3D0) at /usr/= =20 > >src.6/sys/ddb/db_main.c:221 > >#5 0x00000000c018d208 in kdb_trap (type=3D107, code=3D0, =20 > >tf=3D0x16e9a4630) at /usr/src.6/sys/kern/subr_kdb.c:473 > >#6 0x00000000c02f6b4c in trap (tf=3D0x16e9a4630) at /usr/src.6/sys/=20 > >sparc64/sparc64/trap.c:307 > >#7 0x00000000c0048fe0 in tl1_trap () > >#8 0x00000000c0048fe0 in tl1_trap () > >Previous frame identical to this frame (corrupt stack?) > > > >Where ddb showed that the panic correctly (see my mail to -current > >entitled 'panic: uma_small_alloc: free page still has mappings!'). >=20 > How can you compare this backtrace with the one in the email. This > backtrace is the result of a trap, not a panic. For a panic, KDB > is entered via kdb_enter(), not kdb_trap() as it is in this case. Regardless, this is what kgdb informed me was the backtrace for the same thread that panicked and I traced with DDB and gdb53. > It is a known issue that kgdb cannot unwind across traps right now. >=20 > >gdb53 also gets it right, but I can't examine other threads to see if > >they had also panicked. >=20 > Do you mean that 'info threads' doesn't work or that 'thread <TID>' > doesn't work in kgdb? I mean that 'info threads' doesn't work in gdb53, which is the only offline debugger one can use on sparc64 that obtains more or less reliable traces. Kris --ReaqsoxgOBHFXBhH Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDB3YrWry0BWjoQKURAurHAKCoGNw7m6Ive3kwiNRXzFGRwWKq6QCgsU7F xkfRfUk7hjxQM46fAlRwU0c= =aneo -----END PGP SIGNATURE----- --ReaqsoxgOBHFXBhH--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050820182755.GA57524>