[Crash-utility] crash version 4.0-3.2 is available

Dave Anderson anderson at redhat.com
Wed Aug 23 17:13:09 UTC 2006


-  Enabled CONFIG_SPARSEMEM support for ia64 kernels; tested on
   RHEL5-alpha (2.6.17-1.2519.4.5.el5).  Without this fix, crash
   would fail during initialization with error message indicating:
   "crash: CONFIG_SPARSEMEM kernels not supported for this architecture"
   (anderson at redhat.com, dwilder at us.ibm.com)

-  Moved read_in_kernel_config() to just after the internal gdb
   module gets initialized.  Without this fix, xen kernels built
   with CONFIG_IKCONFIG would fail during initialization indicating:
   "crash: gdb_interface: gdb not initialized?"
   (anderson at redhat.com, moriwaka at valinux.co.jp)

-  Implemented new s390/s390x command "s390dbf" command to print out
   kernel traces from the s390 debug feature (s390dbf). The debug
   feature is an s390 kernel trace API which uses wraparound buffers
   to store trace records in memory.  Many of the s390 device drivers
   use this feature.  There is some documentation of the s390dbf in
   the kernel sources under /Documentation/s390/s390dbf.txt.
   (holzheu at de.ibm.com)

-  RHEL5-alpha kernel modules (only x86_64 confirmed) may possibly
   fail to be loaded with the "mod" command due to dwarf2 errors
   associated with the the split module.ko/module.ko.debug debuginfo
   facility used by RHEL kernels.  Bugzillas have been filed to
   address those problems, but the crash utility's error-reporting
   mechanism has beem modified to properly reflect that the internal
   gdb module has failed to load the kernel module's debug data.
   Without this fix, the "mod -[sS]" commands would silently return
   without loading the module data because the "add-symbol-file"
   operation inside the gdb module failed, did a longjmp(), and ended
   up back at the crash prompt.  That behaviour has been changed
   to report the module name and the gdb error like so:

     crash> mod -S
     mod: /lib/modules/2.6.17-1.2564.1/kernel/drivers/scsi/scsi_mod.ko
     gdb add-symbol-file command failed
     crash>

   Note that this problem occurs in all post-RHEL4 kernels, i.e.,
   FC4, FC5, and now FC6 and RHEL5.
   (anderson at redhat.com)

-  Fix for runaway unkillable "repeat" command output that can happen
   when scrolling is turned off and the command that was entered is
   bogus.  (anderson at redhat.com)

-  Fix for "struct structure.member address" output when the member
   is an array; additional members beyond the array contents would
   get displayed.  (anderson at redhat.com)

-  Fix to internal gdb module to properly handle relocatable kernel
   virtual addresses; this will be required for upcoming relocatable
   RHEL5 kernels required for the kexec/kdump facility.
   (anderson at redhat.com)

-  Combined kernel_init(PRE_GDB) and kernel_init(POST_GDB) into a
   single call to kernel_init() that is done after gdb is initialized;
   verify_version() now called by kernel_init().  This is just a code
   re-work, and does not change any functionality. (anderson at redhat.com)


Download from: http://people.redhat.com/anderson

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/crash-utility/attachments/20060823/7e87d659/attachment.htm>


More information about the Crash-utility mailing list