Accepted crash 6.1.3-1 (source amd64)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Wed, 13 Feb 2013 09:28:40 -0700
Source: crash
Binary: crash
Architecture: source amd64
Version: 6.1.3-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.1.3-1) unstable; urgency=low
.
* New upstream version 6.1.3
.
* Implemented a new "crash --log dumpfile" option which dumps the
kernel log buffer and exits. A kernel namelist is not required,
but the dumpfile must contain the VMCOREINFO data from the ELF
header of the original /proc/vmcore file that was created by the
kexec/kdump facility. Accordingly, this option supports kdump ELF
vmcores and compressed kdump vmcores created by the makedumpfile
facility, including those that are in makedumpfile's intermediary
"vmcore.flat" format.
.
* Fixes for the ppc64.c file to handle gcc-4.7.2 compiler warnings when
building crash with "make warn", or compiler failures when building
with "make Warn" on a PPC64 machine. Without the patch, gcc-4.7.2
generates three "error: variable ‘<variable>’ set but not used
[-Werror=unused-but-set-variable]" messages.
.
* Update the PPC64 architecure's internal storage of the kernel's
MAX_PHYSMEM_BITS value for Linux 3.7 and later kernels, which changed
from 44 to 46 to for 64TB support. Without the patch, there is no
known issue, but the stored value should be correct.
.
* Fix for the "mount" command's header display to indicate "MOUNT"
instead of "VFSMOUNT" on Linux 3.3 and later kernels because the
the first column contains a mount structure address instead of a
vfsmount structure address. For those later kernels, it is
permissable to enter either the mount structure address, or the
address of the vfsmount structure that is embedded within it, as
an optional argument. The output has also been tightened up so
that the DIRNAME field is not shifted to the right based upon the
DEVNAME field length.
.
* Fix for the "mount <superblock>" search option on 2.6.32 and later
kernels. Without the patch, it is possible that multiple filesystems
will be displayed.
.
* Update to the "mount" help page to indicate that a dentry address
may be used as a search option.
.
* Fix for the "ps -l [pid|task|command]" option to display the
specified tasks sorted with the most recently-run task (the largest
last_run/timestamp) shown first, as is done with the "ps -l" option
with no arguments. Without the patch, the timestamp data gets
displayed in the order of the "[pid|task|command]" arguments.
.
* Added the "ps" command to the set of supported "foreach" commands,
serving as an alternative manner of passing task-identifying
arguments to the "ps" command. For example, a command such as
"foreach RU ps" can be accomplished without having to pipe normal
"ps" output to "grep RU". All "ps" options are supported from the
"foreach" framework.
.
* Fix for the "ps -G" restrictor option such that it also takes affect
if the -p, -c, -l, -a, -r or -g options are used. Without the
patch, thread group filtering would only take effect when the default
"ps" command is used without any of the options above.
.
* Fortify the internal hq_open() function to return FALSE if it is
already open, and have restore_sanity() and restore_ifile_sanity()
call hq_close() unconditionally.
.
* Added the "extend" command to the set of built-in commands that
support minimal mode. A new MINIMAL flag has been created for
extension modules to set in their command_table_entry.flags field(s)
to signal that a command supports minimal mode. If the crash session
has been invoked with --minimal, then the "extend" command will
require that the module registers at least one command that has
the MINIMAL bit set.
.
* Prevent the "__crc_*" symbols from being added to the the ARM kernel
symbol list.
.
* Prevent the "PRRR" and "NMRR" absolute symbols from being added to
the ARM kernel symbol list. Without the patch, it allows an invalid
set of addresses to pass the check in the in_ksymbol_range() function.
.
* Fix for the ppc.c file to handle a gcc-4.7.2 compiler warning when
building crash with "make warn", or compiler failures when building
with "make Warn" on a PPC machine. Without the patch, gcc-4.7.2
generates the message "error: variable ‘dm’ set but not used
[-Werror=unused-but-set-variable]".
.
* Workaround for the "crash --osrelease dumpfile" option to be able
to work with malformed ARM compressed kdump headers. ARM compressed
kdumps that indicate header version 3 may contain a malformed
kdump_sub_header structure with offset_vmcoreinfo and size_vmcoreinfo
fields offset by 4 bytes, and the actual vmcoreinfo data is not
preceded by its ELF note header and its "VMCOREINFO" string. This
workaround finds the vmcoreinfo data and patches the stored header's
offset_vmcoreinfo and size_vmcoreinfo values. Without the patch, the
"--osrelease dumpfile" command line option fails with the message
"crash: compressed kdump: cannot lseek dump vmcoreinfo", followed by
"unknown".
.
* Fix for the "help -n" option on 32-bit compressed kdumps. Without
the patch, the offset_vmcoreinfo, offset_eraseinfo, and offset_note
fields of the kdump_sub_header have their upper 32-bits clipped off
when displayed. However, it should be harmless since the offset
values point into the first few pages of the dumpfile.
.
* Update of the extensions/echo.c extension module example, and the
"extend" help page, to utilize a constructor function to call the
register_extension() function. The _init() and _fini() functions
have been designated as obsolete for usage by dlopen() and dlclose().
The echo.c example module has been modified to contain echo_init()
and echo_fini() functions marked as __attribute__((constructor)) and
__attribute__((destructor)) respectively.
.
* Updated extensions/dminfo.c, extensions/snap.c and extensions/trace.c
to replace their _init() and _fini() functions with constructor and
destructor functions.
.
* Fix for the "bt" command on the PPC64 architecture when running
on Linux 3.7 kernel threads. Without the patch, some kernel threads
may fail to terminate on the final ".ret_from_kernel_thread" frame,
repeating that frame endlessly, because the stack linkage pointer
points back to itself instead of being NULL.
Checksums-Sha1:
7d79d4eedb626fdb967c7af108e8836a6eaaf7e8 1084 crash_6.1.3-1.dsc
bc18327939faa141768616681ad04456fcdf19f6 26781324 crash_6.1.3.orig.tar.gz
bd5d85b1b6ad452aa3e142156884f068a7d50856 56486 crash_6.1.3-1.diff.gz
1df074e7b9d439ade2b051f03626bd538686f254 2661888 crash_6.1.3-1_amd64.deb
Checksums-Sha256:
9746b369a296615aaf53bead1d2ffc4e33bd001831b2bc7d243713bf55eef995 1084 crash_6.1.3-1.dsc
690a8ed50240f1a3ff29c9a2bfe56d4b1355f64e184892c12d546ba8c377ba3d 26781324 crash_6.1.3.orig.tar.gz
2b01bfc2706a96254f866e9e20f3378a55aa51baa97cfe51ab2c0653142894cf 56486 crash_6.1.3-1.diff.gz
db2e7441a8ebd1fa45d0a98b157e83738036bcaaf597f603f6e2fa8d0186c85a 2661888 crash_6.1.3-1_amd64.deb
Files:
4b20ea528c79c51b20cd1f2998ac5b05 1084 utils optional crash_6.1.3-1.dsc
240930db5cbd5ef55ea654348c2fa961 26781324 utils optional crash_6.1.3.orig.tar.gz
036c2d6485e8a8309e834603e0beafed 56486 utils optional crash_6.1.3-1.diff.gz
e575a2b975f01b7f50e38bf12689196a 2661888 utils optional crash_6.1.3-1_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iD8DBQFRG8inQOr9C+GfGI4RAhnhAJ99qXHO5ljKsrP1Wq7/GMEJSyvWswCfbM65
l/4kx1B3NKzK80V83nZP/Rw=
=EScR
-----END PGP SIGNATURE-----
Reply to: