Date: Wed, 13 Oct 2004 17:27:47 +0900 From: Pyun YongHyeon <yongari@kt-is.co.kr> To: Maxim Konovalov <maxim@macomnet.ru> Cc: freebsd-sparc64@freebsd.org Subject: Re: sparc64 kernel dump debug Message-ID: <20041013082747.GA8594@kt-is.co.kr> In-Reply-To: <20041012154552.E60900@mp2.macomnet.net> References: <20041012154552.E60900@mp2.macomnet.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Oct 12, 2004 at 04:17:46PM +0400, Maxim Konovalov wrote: > [Bcc: sparc64@ ] > > Hello, > > Are there any ways to debug a kernel dump on sparc64? On our SMP > netra1440: > > # strings vmcore.3 | grep panic > panic: trap: fast data access mmu miss > ... > > # kgdb kernel.debug vmcore.3 2>&1| more > kgdb: kvm_read: invalid address (71756972) > kgdb: kvm_read: invalid address (4580a0) > kgdb: kvm_read: invalid address (1) > kgdb: kvm_read: invalid address (1) > kgdb: kvm_read: invalid address (1) > kgdb: kvm_read: invalid address (1) > ... > > # uname -a > FreeBSD sun4u 6.0-CURRENT FreeBSD 6.0-CURRENT #2: Fri > Oct 1 12:02:51 MSD 2004 root@sun4u:/usr/obj/usr/src/sys/SUN4U sparc64 > AFAIK, neither gdb6 from ports nor kgdb works on sparc64. So I use trace command in DDB prompt and have to use addr2line(1) to get source location. Or you can use objdump(1). > -- > Maxim Konovalov -- Regards, Pyun YongHyeon http://www.kr.freebsd.org/~yongari | yongari@freebsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041013082747.GA8594>