atom feed6 messages in org.freebsd.freebsd-currentRe: Crash dumps on current
FromSent OnAttachments
M. Warner LoshJul 9, 2002 9:01 am 
Dan NelsonJul 9, 2002 9:20 am 
David W. Chapman Jr.Jul 9, 2002 9:33 am 
John BaldwinJul 9, 2002 9:46 am 
Matthew DillonJul 9, 2002 10:36 am 
Alex ZepedaJul 9, 2002 11:45 pm 
Subject:Re: Crash dumps on current
From:David W. Chapman Jr. (dwc@inethouston.net)
Date:Jul 9, 2002 9:33:52 am
List:org.freebsd.freebsd-current

On Tue, Jul 09, 2002 at 11:20:52AM -0500, Dan Nelson wrote:

In the last episode (Jul 09), M. Warner Losh said:

OK. How the ***** do I get a *!@#$@$#% crash dump on current? I did a dumpon to enable the dumping, which appeared to work. I then did a savecore after the system came back up (but before any swapping happened) and that seemed to work. I then tried to use gdb to read the core dump and got the following:

sudo gdb -k ~/FreeBSD/src/sys/i386/compile/GENERIC/kernel.debug vmcore.2 GNU gdb 4.18 (FreeBSD) Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"...Deprecated bfd_read called
at /dell/imp/FreeBSD/src/contrib/gdb/gdb/dwarf2read.c line 3049 in
dwarf2_read_section

Dwarf Error: Cannot handle DW_FORM_strp in DWARF reader.

Don't you need to use gdb52 -k now, since the new GCC was turned on?

gdb52 was imported into -current a week or two ago. It does look like he does either need to use the port or upgrade -current.

-- David W. Chapman Jr. dwc@inethouston.net Raintree Network Services, Inc. <www.inethouston.net> dwc@freebsd.org FreeBSD Committer <www.FreeBSD.org>

To Unsubscribe: send mail to majo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message