Date: Mon, 09 Nov 2015 12:16:38 -0800 From: John Baldwin <jhb@freebsd.org> To: freebsd-current@freebsd.org Cc: Hans Petter Selasky <hps@selasky.org>, Andriy Gapon <avg@freebsd.org>, FreeBSD Current <freebsd-current@freebsd.org>, FreeBSD Hackers <freebsd-hackers@freebsd.org> Subject: Re: strange kernel crash Message-ID: <2278845.gkxYBUMIWE@ralph.baldwin.cx> In-Reply-To: <563CEB53.50909@selasky.org> References: <563C8CED.3020101@FreeBSD.org> <563CEB53.50909@selasky.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday, November 06, 2015 07:02:59 PM Hans Petter Selasky wrote: > On 11/06/15 12:20, Andriy Gapon wrote: > > Now the strange part: > > > > 0xffffffff80619a18 <+744>: jne 0xffffffff80619a61 <__mtx_lock_flags+817> > > 0xffffffff80619a1a <+746>: mov %rbx,(%rsp) > > => 0xffffffff80619a1e <+750>: movq $0x0,0x18(%rsp) > > 0xffffffff80619a27 <+759>: movq $0x0,0x10(%rsp) > > 0xffffffff80619a30 <+768>: movq $0x0,0x8(%rsp) > > Were these instructions dumped from RAM or from the kernel ELF file? Probably not from RAM. You can use 'info files' in gdb to see what is handling the address range in question (core vs executable). x/i in ddb would have been the "real" truth. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2278845.gkxYBUMIWE>