Date: Fri, 16 Apr 2004 17:26:54 +0930 From: "Daniel O'Connor" <doconnor@gsoft.com.au> To: Philip Paeps <philip@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: GDB broken? Message-ID: <200404161726.54783.doconnor@gsoft.com.au> In-Reply-To: <20040416072414.GJ688@loge.nixsys.be> References: <200404161447.29595.doconnor@gsoft.com.au> <20040416072414.GJ688@loge.nixsys.be>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 16 Apr 2004 16:54, Philip Paeps wrote: > On 2004-04-16 14:47:29 (+0930), Daniel O'Connor <doconnor@gsoft.com.au> wrote: > > I was helping someone test patches in -current and got a crash dump, but > > GDB doesn't like reading it.. > > I've also seen this happen a few times in the past. > > > [inchoate 14:45] /var/crash >sudo gdb -k /boot/kernel/kernel > > /var/crash/vmcore.1 GNU gdb 5.2.1 (FreeBSD) > > Did you make that core by calling doadump, or by calling panic in the > debugger? I found that GDB will happily eat plain panic cores, but doesn't > appear to like doadump cores. I've only tested with two corefiles though, > so I might be wrong. Anyone else care to test? It was doadump.. I had trouble with panic panic'ing and not dumping when I've tried it in the past :( I'll keep it in mind though. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 9A8C 569F 685A D928 5140 AE4B 319B 41F4 5D17 FDD5
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200404161726.54783.doconnor>