Date: Wed, 19 Nov 2003 15:13:55 +0000 (UTC) From: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> To: Robert Watson <rwatson@freebsd.org> Cc: Hajimu UMEMOTO <ume@mahoroba.org> Subject: Re: another trap 12 while in kernel mode Message-ID: <Pine.BSF.4.53.0311191504260.92260@e0-0.zab2.int.zabbadoz.net> In-Reply-To: <Pine.NEB.3.96L.1031119095002.7131C-100000@fledge.watson.org> References: <Pine.NEB.3.96L.1031119095002.7131C-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 19 Nov 2003, Robert Watson wrote: Hi, > You should still be able to turn the bad instruction pointer into at least > a function name using nm on your compiled kernel. Run nm on the kernel > binary, and search through it until you find the symbols just before > (lower) and just after (higher) than the value listed for the instruction > pointer below. That would at least tell us what function the fault is > occuring in. I suspect to get anywhere useful, we'll need the full > debugging results, but it's probably a useful start, and it will allow us > to be sure the panics you might get after you have debugging support > compiled in are the same failure mode. thanks for your answer. > > instruction pointer = 0x8:0xc055a00a c0559e10 T key_sa_routechange c0559f10 t key_sa_chgstate c0559fb0 T key_sa_stir_iv c0559fe0 t key_sp_dead c0559ff0 t key_sp_unlink c055a020 t key_alloc_mbuf c055a100 t kdebug_typestr c055a150 t kdebug_sadb_msg_typestr c055a170 t kdebug_sadb_ext_typestr Cc'ed ume. -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT 56 69 73 69 74 http://www.zabbadoz.net/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.53.0311191504260.92260>