Branches for Wheezy

Author: Troy Heber
Revision Date: 2012-05-10 09:18:26 UTC

* New upstream version 6.0.6
* Extend the supported cross-architecture build capability so that it
  applies to the SIAL extension module. Without the patch, when building
  the SIAL module in an environment where the overlying crash utility was
  built with "make target=ARM", "make target=PPC", or "make target=X86", the
  SIAL extension module would continue to be built for the host
  architecture.
* Fixes for memory leaks and possible segmentation violations when unloading
  SIAL extension module scripts.
* Fix for the new "foreach RU" task state qualifier. Without the patch, the
  runnable tasks are not selected.
* Fix to disallow multiple task states from being entered using the "foreach
  <task-state>" qualifier. Without the patch, if multiple states were
  entered, the last one on the command line would be honored.
* Fix for the "extend" command to allow the usage of 32-bit PPC extension
  modules. Without the patch, the command fails with the message: "extend:
  <object>.so: not an ELF format object file".
* If an input line starts with "#" or "//", then the line will be saved as a
  comment that is visible when re-cycling through the command history list.
* Fix for a crash-5.1.9 regression that broke the "bt -g" option. Without
  the patch, the option is ignored completely.
* Fix for s390x virtual-to-physical translation of virtual addresses that
  are backed by 1MB pages.
* The s390x has a dumpfile method that creates "live dumps", where the
  kernel continues to run while the dumpfile is being created. The initial
  system banner display and the "sys" command will inform the user that the
  dumpfile is a "[LIVE DUMP]", and the "bt -a" option will fail with the
  message "bt: -a option not supported on a live system or live dump".
* Newly-created dumpfiles generated by the "snap.c" extension module will
  now be recognized as "live dumps". Accordingly, the initial system banner
  display and the "sys" command will inform the user that the dumpfile is a
  "[LIVE DUMP]", and the "bt -a" option will fail with the message "bt: -a
  option not supported on a live system or live dump".
* If "bt" alone is attempted on an active task in a "live dump", it will
  indicate "(active)", i.e., the same as if it were attempted on a live
  system.
* If an extension module does not define the appropriate architecture, i.e.,
  "-DX86", "-DX86_64", etc., then the inclusion of "defs.h" will generate a
  compiler failure indicating "error: 'NR_CPUS' undeclared here (not in a
  function)". In that case, the architecture will now default to that of
  the host machine.
* Prevent a highly-unlikely incorrect calculation of the maximum cpudata
  array length of a kmem_cache during initialization of of CONFIG_SLAB
  kernels.
* Prevent an infinite loop during the initialization of the kmem_cache
  subsystem in CONFIG_SLAB kernels if the cache list or the vmcore is
  corrupt. If the kmem_cache list links back into itself, messages showing
  the first "duplicate" entry in the list and "crash: unable to initialize
  kmem slab cache subsystem" will be displayed.
* Update to the "mod" command to additionally search for module object files
  in the directory containing the kernel namelist (vmlinux) file. This will
  allow an alternate module-debuginfo directory tree to be set up like so: #
  cd <directory> # rpm2cpio kernel-debuginfo-<release>.rpm | cpio -idv
  Having done that, and by referencing the vmlinux file in that directory
  tree directly or by symbolic link, the "mod" command will search for
  module object files starting from the directory containing the vmlinux
  file if they are not found in the standard /lib/modules/<release>
  directory.
* Update to the s390x "bt" command if a task was running in userspace.
  Without the patch, the back trace display ended at the kernel entry
  function frame; with the patch, the user space PSW register is displayed
  with a "(user space)" tag, followed by the general purpose register set.
* In the unlikely event that the access of ARM or x86_64 kernel unwind table
  data fails during crash invocation, print a warning message and allow the
  crash session to continue. Without the patch, the crash session would
  fail immediately.