Crash exits with an error "cannot determine pid_hash
array
dimensions". Looking at the crash change log, it
appears that it was
fixed in 4.0-2.24 for the 2.6.17 kernel. The core I have is
of a
2.6.16.13 xenified kernel. Is the fix even relevant ?
<output>
$ ./crash vmlinux-2.6.16.13-xen test.core
crash 4.0-3.5
Copyright (C) 2002, 2003, 2004, 2005, 2006 Red Hat, Inc.
Copyright (C) 2004, 2005, 2006 IBM Corporation
Copyright (C) 1999-2006 Hewlett-Packard Co
Copyright (C) 2005 Fujitsu Limited
Copyright (C) 2005 NEC Corporation
Copyright (C) 1999, 2002 Silicon Graphics, Inc.
Copyright (C) 1999, 2000, 2001, 2002 Mission Critical
Linux, Inc.
This program 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. Enter "help copying" to see
the conditions.
This program has absolutely no warranty. Enter "help
warranty" for details.
GNU gdb 6.1
Copyright 2004 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
"x86_64-unknown-linux-gnu"...
please wait... (gathering task table data)
crash: cannot determine pid_hash array dimensions
</output>
Is there a way I can get crash's source at releases
4.0-2.24 and
4.0-2.23 so that I can try a fix for this kernel in case it
is a
specific kernel fix ?
Thanks
-Tejasvi
--
Crash-utility mailing list
Crash-utility redhat.com
https://www.redhat.com/mailman/listinfo/crash-utility
|