-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.8 Date: Thu, 14 Jul 2011 15:15:13 -0600 Source: crash Binary: crash Architecture: source amd64 Version: 5.1.7-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 (5.1.7-1) unstable; urgency=low . * New upstream version 5.1.7 * Fix for the x86_64 "bt" command in the highly-unlikely event that a non-crashing CPU receives a NMI immediately after receiving an interrupt from another source in a 2.6.29 and later kernel. In those kernels, the IRQ entry-point symbols "IRQ0x00_interrupt" through "IRQ0x##_interrupt" no longer exist, but the entry points exist as memory locations starting at the symbol "irq_entries_start". Without the patch, if a shutdown NMI interrupt gets received while in one of the entry point stubs, "bt" will fail with the error message "bt: cannot transition from exception stack to current process stack". * The x86 and x86_64 "bt -e" and "bt -E" commands will display symbolic translations of kernel-mode exception RIP values. * Clarified two initialization-time CRASHDEBUG(1) messages to make it obvious that the two linux_banner strings being compared originate from the memory source or the kernel namelist file. * Fix for the x86 "bt" command to handle cases where the shutdown NMI was received when a task had just completed an exception, interrupt, or signal handler, and was about to return to user-space. Without the patch, the backtrace would be proceeded with the error message "bt: cannot resolve stack trace", display the trace without the kernel-entry exception frame, and then dump the text symbols found on the stack and all possible exception frames. * Fix for 2.6.33 and later kernels that are not configured CONFIG_SMP. Without the patch, they fail during initialization with the error message "crash: invalid structure member offset: module_percpu". * Prepare for the imminent change in size of the vm_flags member of the vm_area_struct to be 64-bits in size for all architectures now that 32 bits have been consumed. The crash utility code had been handling the older change of the vm_flags member from a short to a long, but that would not account for the future change to a 64-bit member on 32-bit architectures. * Update of the "vm -f <flags>" option to the current upstream state. Without the patch, only 23 of the currently-existing 32 bit flags were being translated. (anderson@redhat.com) * Fix for the "kmem -s", "kmem -S", "kmem -s <address>" and "kmem <address>" command options if none of the NUMA nodes in in a multi-node CONFIG_SLAB system have a node ID of 0. Without the patch, "kmem -s" and "kmem -S" show all slab caches as if they contain no slabs; if an <address> is specified, the correct slab cache is found, but the command indicates "kmem: <slab-cache-name>: address not found in cache: <address>". * Cosmetic fix for the "kmem -[sS]" options if a CONFIG_SLAB kernel slab cache contains 100000 or more slabs, or uses a slab size of 1 or more megabytes. Without the patch, the output utilizes more than 80 columns. * If a task was in user-space when a crash occurred, the user-space registers are saved in per-cpu NT_PRSTATUS ELF notes in either version 4 compressed kdump headers, or in dumpfile headers created by the Fujitsu "sadump" facility. In that case, the "bt" command will dump the x86 or x86_64 user-space register set. * Fix for the x86 "bt" command to handle cases where the shutdown NMI was received when a task had just received an interrupt, but before it had created a full exception frame on the kernel stack and called the interrupt handler. Without the patch, the backtrace would be proceeded with the error message "bt: cannot resolve stack trace", display the trace without the kernel-entry exception frame, and then dump the text symbols found on the stack and all possible exception frames. * Fix for the x86 "bt" command to handle cases where the shutdown NMI was received when a task was in the act of being switched to. Without the patch, the backtrace would be proceeded with the error message "bt: cannot resolve stack trace", display the trace without the kernel-entry exception frame, and then dump the text symbols found on the stack and all possible exception frames. Checksums-Sha1: 2aa274181efe8951636f554930193303442f32a0 1017 crash_5.1.7-1.dsc df48188cc7d02b660666a8799c7e7835cb0979e2 24396827 crash_5.1.7.orig.tar.gz c832213d77fc8781eaa5519980ab57c35e88bdcb 30367 crash_5.1.7-1.diff.gz 38b7f3f346bb98f48f14c1476cfae3086710f56f 2422726 crash_5.1.7-1_amd64.deb Checksums-Sha256: b5057bd8205e2bb46d38d809a5f27cbfef2c69dccef6842be174af622db2f1e9 1017 crash_5.1.7-1.dsc 5233ffcaad72652b1f5f8822553a5094537e864cdbc13ac8da39697e670da5da 24396827 crash_5.1.7.orig.tar.gz 96fdeb073388f0a467726b0a25c1e74d561be7f4e4554620a8adf1093aa40fd0 30367 crash_5.1.7-1.diff.gz 6173007057c3aa96094031c2c809367b0254effe8b37954a29d7e199c1dc848b 2422726 crash_5.1.7-1_amd64.deb Files: 0f714d290575150ce49579fd248302d3 1017 utils optional crash_5.1.7-1.dsc 8654c5577691d3f5602443689e7214a2 24396827 utils optional crash_5.1.7.orig.tar.gz e6b2ae30c6d786a3c684557b490a293e 30367 utils optional crash_5.1.7-1.diff.gz 98c4a2128d99520b27ec5e3bdbb2532a 2422726 utils optional crash_5.1.7-1_amd64.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iD8DBQFOIGgvQOr9C+GfGI4RArKCAKCwkMSfStQWAZqwIYDkacz2o+QY7ACeN7LS 9Ipb/qBphLyU8mjU1rjnoOU= =JqlO -----END PGP SIGNATURE----- Accepted: crash_5.1.7-1.diff.gz to main/c/crash/crash_5.1.7-1.diff.gz crash_5.1.7-1.dsc to main/c/crash/crash_5.1.7-1.dsc crash_5.1.7-1_amd64.deb to main/c/crash/crash_5.1.7-1_amd64.deb crash_5.1.7.orig.tar.gz to main/c/crash/crash_5.1.7.orig.tar.gz