Accepted crash 6.0.6-1 (source amd64)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Thu, 10 May 2012 09:18:26 -0600
Source: crash
Binary: crash
Architecture: source amd64
Version: 6.0.6-1
Distribution: unstable
Urgency: low
Maintainer: Troy Heber <troyh@debian.org>
Changed-By: Troy Heber <troyh@debian.org>
Description:
crash - kernel debugging utility, allowing gdb like syntax
Changes:
crash (6.0.6-1) unstable; urgency=low
.
* 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.
Checksums-Sha1:
35850c6335d7a5e14a70b34158111e49dd7cdc1c 1084 crash_6.0.6-1.dsc
594523d13d4494d188d64423958b9ff52a12e064 26831731 crash_6.0.6.orig.tar.gz
c54c37ee156520253bb60299427bd2e091193bfb 43258 crash_6.0.6-1.diff.gz
584cab5fe4fb22770c7755079a54fbe3dafb42f5 2608768 crash_6.0.6-1_amd64.deb
Checksums-Sha256:
0042b2c1d85ab363dbc04aaa49d15d05ec6bf5282df536ec1a8310d61641d8c7 1084 crash_6.0.6-1.dsc
9c679f4911846e1f756f4926eead9f6bf30fe033fecf64e937066ed8fca4d4e0 26831731 crash_6.0.6.orig.tar.gz
fc87ac17fe5a1555302ee07f1c31131285e8faca20363b823492f2be28398866 43258 crash_6.0.6-1.diff.gz
fef03ba37df52476eca20b06fdff5a79b5f4001b3fa33d0fb7062718f5f510c3 2608768 crash_6.0.6-1_amd64.deb
Files:
025a1cad6d5cc0c2eca25431ae172172 1084 utils optional crash_6.0.6-1.dsc
3b567a5df156d2e5482ddf587f2f8975 26831731 utils optional crash_6.0.6.orig.tar.gz
273169587eb959e00c13b96d58ac2004 43258 utils optional crash_6.0.6-1.diff.gz
699389555ed39c0808e274cbba63220e 2608768 utils optional crash_6.0.6-1_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iD8DBQFPq+EeQOr9C+GfGI4RAtxJAKChuYjD3ahc66NPoZsJ1mv+kT0WEwCguHoM
CHopixsDLgViHC99vmNxiEk=
=GFEA
-----END PGP SIGNATURE-----
Accepted:
crash_6.0.6-1.diff.gz
to main/c/crash/crash_6.0.6-1.diff.gz
crash_6.0.6-1.dsc
to main/c/crash/crash_6.0.6-1.dsc
crash_6.0.6-1_amd64.deb
to main/c/crash/crash_6.0.6-1_amd64.deb
crash_6.0.6.orig.tar.gz
to main/c/crash/crash_6.0.6.orig.tar.gz
Reply to: