I can see that the new version has made it into testing, I was wondering
if there is a plan to update the version in Jessie backports as well.
Thanks,
Mike Bacco
On Mon, 02 May 2016 13:22:04 +0000 Troy Heber <tr...@debian.org> wrote:
Source: crash
Source-Version: 7.1.5-1
We believe that the bug you reported is fixed in the latest version of
crash, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 817...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Troy Heber <tr...@debian.org> (supplier of updated crash package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Sat, 30 Apr 2016 07:54:33 -0600
Source: crash
Binary: crash
Architecture: source amd64
Version: 7.1.5-1
Distribution: unstable
Urgency: medium
Maintainer: Troy Heber <tr...@debian.org>
Changed-By: Troy Heber <tr...@debian.org>
Description:
crash - kernel debugging utility, allowing gdb like syntax
Closes: 817798
Changes:
crash (7.1.5-1) unstable; urgency=medium
.
* New upstream 7.1.5 (Closes: #817798):
.
* Fix for the handling of Xen DomU ELF dumpfiles to prevent the
pre-gathering of p2m frames during session initialization, which is
unnecessary since ELF files contain the mapping information in their
".xen_p2m" section. Without the patch, it is possible that the crash
session may be unnecessarily aborted if the p2m frame-gathering fails, for
example, if the CR3 value in the header is invalid.
.
* Fix for the translation of X86_64 virtual addresses in the vsyscall region
between 0xffffffffff600000 and 0xffffffffffe00000. Without the patch, the
reading of addresses in that region returns invalid data; in addition, the
"vtop" command for an address in that region shows an invalid physical
address under the "PHYSICAL" column.
.
* Make the "zero excluded" mode default behavior when analyzing SADUMP
dumpfiles because some Fujitsu troubleshooting software assumes the
behavior. Also, fix the "set -v" option to show the "zero_excluded"
internal variable as "on" if it has been set when analyzing SADUMP
