----- "Nipul Gandhi" <noreplyever@xxxxxxxxx> wrote: > Hi all - > > What am I doing wrong here ? > > > > [root@wal-rhel5-04 kern]# uname -a > Linux wal-rhel5-04 2.6.18-92.el5 #1 SMP Tue Apr 29 13:16:15 EDT 2008 > x86_64 x86_64 x86_64 GNU/Linux > > > Using the installed by this debuginfo RPM: > > kernel-debuginfo-common-2.6.18-92.el5 > kernel-debug-debuginfo-2.6.18-92.el5 > > > [root@wal-rhel5-04 kern]# crash /usr/lib/debug/lib/modules/2.6.18-92.el5debug/vmlinux > > ... > > WARNING: /usr/lib/debug/lib/modules/2.6.18-92.el5debug/vmlinux > and /proc/version do not match! > > WARNING: /proc/version indicates kernel version: 2.6.18-92.el5 > > crash: please use the vmlinux file for that kernel version, or try using > the System.map for that kernel version as an additional argument. > > [root@wal-rhel5-04 tmp]# cat /proc/version > Linux version 2.6.18-92.el5 (brewbuilder@xxxxxxxxxxxxxxxxxxxxxxxxxxxx) > (gcc version 4.1.2 20071124 (Red Hat 4.1.2-41)) #1 SMP Tue Apr 29 > 13:16:15 EDT 2008 > > I tried using the System.Map as well as argument.....but then it segfaulted. > # crash /usr/lib/debug/lib/modules/2.6.18-92.el5debug/vmlinux /boot/System.map-2.6.18-92.el5 > > Segmentation fault (core dumped) > > Thanks in advance for any help. You're invoking crash with the "2.6.18-92.el5debug" kernel, but the live system is running the "2.6.18-92.el5". They are completely different kernels. (The "debug" variant has all sorts of debugging configs turned on) So, for example, on an x86_64 machine, you would need to install: kernel-debuginfo-2.6.18-92.el5.x86_64.rpm kernel-debuginfo-common-2.6.18-92.el5.x86_64.rpm After you do that, you only need to enter "crash" alone on the command line, and it will find the vmlinux file automatcally based upon what it sees in /proc/version. Dave -- Crash-utility mailing list Crash-utility@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/crash-utility
