New subject: SLES 9 Dump

Tuesday, 5 March 2013

...
 I tried again using kerntypes and it failed with a different error.

 # /RedHat/crash-6.1.0-X86/crash vmlinux-2.6.5-7.321-bigsmp dump-pts02504
 Kerntypes-2.6.5-7.321-bigsmp
 ...
 crash: cannot resolve "_stext"

 Eugene 
Try putting *both* the System.map file (required for _stext) and
the Kerntypes file (required for debuginfo data) on the command
line.

If there is really no "_stext" symbol in the System.map file, then
you're screwed.  Although, I would have presumed that it could get
the _stext symbol from the stripped vmlinux file.  If you do
"nm -Bn vmlinux", does it show an _stext symbol?

Dave

Dave

...

 -----Original Message-----
 From: Ku, Eugene
 Sent: Tuesday, March 05, 2013 6:04 PM
 To: Dave Anderson
 Cc: Ku, Eugene
 Subject: RE: [Crash-utility] SLES 9 Dump

 Dave,

 I rebuilt 6.1.0 crash as you had suggested.

 # file /RedHat/crash-6.1.0-X86/crash
 /RedHat/crash-6.1.0-X86/crash: ELF 32-bit LSB executable, Intel 80386,
 version 1 (SYSV), for GNU/Linux 2.6.9, dynamically linked (uses shared
 libs), for GNU/Linux 2.6.9, not stripped

 I then ran it against the dump.  I got the following error messages.

 # /RedHat/crash-6.1.0-X86/crash vmlinux-2.6.5-7.321-bigsmp dump-pts02504
 ...
 crash: vmlinux-2.6.5-7.321-bigsmp: no debugging data available

 I tried again with additional System.map but got the same error.

 # /RedHat/crash-6.1.0-X86/crash vmlinux-2.6.5-7.321-bigsmp dump-pts02504
 System.map-2.6.5-7.321-bigsmp
 ...
 crash: vmlinux-2.6.5-7.321-bigsmp: no debugging data available

 Eugene

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

Re: [Crash-utility] SLES 9 Dump