Re: reading kernel dump - post gcc 3.1
Am Mo, 2002-05-27 um 19.52 schrieb David O'Brien: On Mon, May 27, 2002 at 12:23:13PM +0200, Georg-W. Koltermann wrote: Please read bin/38236. I wasn't asking for general directions but for a specific solution to a current -current problem. RTFM specifically the -gstabs+ GCC option. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message Hi David, are you saying that I should compile my _kernel_ with -gstabs+, since this is a problem reading a kernel dump? If so, would you mind adding a short note to UPDATING? -- Thanks, Georg. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: reading kernel dump - post gcc 3.1
Am Sa, 2002-05-25 um 02.30 schrieb Craig Carey: [...] savecore(8) should copy a dump of the crashed kernel to /var/crash and created files kernel.0 and vmcore.0. gdb -k kernel.0 vmcore.0 hunter[13]$ gdb -k kernel.debug vmcore.19 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... Dwarf Error: Cannot handle DW_FORM_strp in DWARF reader. kernel symbol `cpuhead' not found. (kgdb) Please read bin/38236. I wasn't asking for general directions but for a specific solution to a current -current problem. -- Thanks, Georg. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: reading kernel dump - post gcc 3.1
On Mon, May 27, 2002 at 12:23:13PM +0200, Georg-W. Koltermann wrote: Please read bin/38236. I wasn't asking for general directions but for a specific solution to a current -current problem. RTFM specifically the -gstabs+ GCC option. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: reading kernel dump - post gcc 3.1
At 02\05\24 14:52 +0200 Friday, Georg-W. Koltermann wrote: Hi, I got a couple of kernel panics recently, some of them buffer not locked. I would like to know how I can get more information out of the dump. The system's gdb does not like the dump format any more, see also bin/38236. There is an advertised workaround in that pr of using gdb52, but I couldn't get that to work (not a core dump: File format not recognized). Am I missing something? How do you guys read your dumps? There are online articles on how to get and read kernel panic dumps, at these webpages. Also I copy parts views the articles. http://www.onlamp.com/pub/a/bsd/2002/03/21/Big_Scary_Daemons.html http://www.onlamp.com/pub/a/bsd/2002/03/21/Big_Scary_Daemons.html?page=2 System Panics, Part 1: Preparing for the Worst (21 March 2002), by Mr. M. Lucas Add: options DDB makeoptions DEBUG=-g to config file. A large enough swap file is needed for the dump. Specify in /etc/rc.conf: dumpdev=/dev/ad0s4b, the dumpdir may be specified to be /var/crash. Read savecore(8). http://www.onlamp.com/pub/a/bsd/2002/04/04/Big_Scary_Daemons.html http://www.onlamp.com/pub/a/bsd/2002/04/04/Big_Scary_Daemons.html?page=2 System Panics, Part 2: Recovering and Debugging (4 April 2002) savecore(8) should copy a dump of the crashed kernel to /var/crash and created files kernel.0 and vmcore.0. gdb -k kernel.0 vmcore.0 __ Craig Carey To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
