Accepted crash 7.0.1-1 (source amd64)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Tue, 18 Jun 2013 13:38:49 -0600
Source: crash
Binary: crash
Architecture: source amd64
Version: 7.0.1-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
Closes: 504522 584119 656132 702513 710675
Changes:
crash (7.0.1-1) unstable; urgency=low
.
* Enable armel (closes: #656132)
* Enable s390x (closes: #710675)
* Include the crash/defs.h header (closes: #702513)
* Sync with the Ubuntu crash package, build crash extensions, SPU has been
dropped (closes: #584119), lpia has been dropped (closes: #504522).
* Fix the -I include path sequence in the extensions/eppic.mk file to
prevent a series of "redefined" and "redeclaration" warnings when
compiling the EPPIC extension module.
* Address two compile-time warnings generated as a result of the
gdb*7.6.patch. Without the patch, there are "warning: no previous
prototype" warnings for gdb_main_entry() and replace_ui_file_FILE().
* Implemented a new "mod -t" option that walks through the installed modules
and checks for non*zero values in each module's "taints" bitmask, and
translates the bits into symbolic letters if possible, or shows the
hexadecimal value of the bitmask if not. In older kernels, the
"license_gplok" field is checked, and if non*zero, its value is displayed
in hexadecimal. Lastly, if the "gpgsig_ok" member exists and is zero, a
"(U)" notation will also be displayed.
* Fixed compiler warnings generated by extensions/trace.c when compiled
with *DFORTIFY_SOURCE=2. Without the patch, the messages "warning:
ignoring return value of 'mktemp', declared with attribute
warn_unused_result", "warning: ignoring return value of 'fwrite',
declared with attribute warn_unused_result", and "warning: 'trace_dat'
may be used uninitialized in this function" are generated.
* Laid down the basic infrastructure for the ARM64 backtrace facility using
the kernel's arm64 unwind facility as a basis. Compile*tested only.
* Implemented the ARM64 virtual-to-physical kernel and user address
translation functions, supporting both 2*level page tables with 64K pages,
and 3*level page tables with 4K pages. Also added the associated PTE
translator function. Compile*tested only.
* Implemented the capability of building crash as an x86_64 binary for
analyzing ARM64 dumpfiles on an x86_64 host, which can be done by entering
"make target=ARM64". After the initial build is complete, subsequent
builds can be done by entering "make" alone.
* Added "aarch64" to the ExclusiveArch: line in the crash.spec file.
* Fix for the S390X "bt" command for Linux 3.10 and later kernels. Without
the patch, the starting stack location of the per*cpu async and panic
stacks of active tasks would be incorrectly determined.
Checksums-Sha1:
45dc610e6197287876d7f00320abc93de250e578 1101 crash_7.0.1-1.dsc
3b9233cba7b92c9df611b9827d32e93390b26717 32013795 crash_7.0.1.orig.tar.gz
413b07bd59a802c7185fe1874dc842381326dfa1 61707 crash_7.0.1-1.diff.gz
fe9bfcda8aa806f09bf72d745901720d7745073f 3062848 crash_7.0.1-1_amd64.deb
Checksums-Sha256:
55da24841cb8ec52c1948b917fc68f2b2dc0c381ab2103b775fa827986cb8aad 1101 crash_7.0.1-1.dsc
131c11e48d70ebaad3e2f1a019be479ca0c892a163561007becc4f3d75619deb 32013795 crash_7.0.1.orig.tar.gz
8ecbde6fbafa62164e6a4aff59c1c3aa91e757482b90eddbd3382fa0d48b598a 61707 crash_7.0.1-1.diff.gz
0a1e101ae057c56a707bb53a59e9e35fe6bf1c1464c57bc1d6bc5b4ad2193635 3062848 crash_7.0.1-1_amd64.deb
Files:
010e1e317c404ca77dbf6bb383e1c520 1101 utils optional crash_7.0.1-1.dsc
b59076aebaced87e9073328cb0a4f50a 32013795 utils optional crash_7.0.1.orig.tar.gz
eefea1bdbbc2488294c7ab9dab2f2faa 61707 utils optional crash_7.0.1-1.diff.gz
651ccd55d6f448775d7be14e88e94ffd 3062848 utils optional crash_7.0.1-1_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iD8DBQFR3Hl3QOr9C+GfGI4RApumAJ0UbwnpYkoApj64Mt1hoAUhCoNDfwCfQFIR
mpkHZ/Vdpg2rT1ag+gCd018=
=d6e5
-----END PGP SIGNATURE-----
Reply to: