Accepted crash 5.1.4-1 (source amd64)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Fri, 01 Apr 2011 09:58:11 -0600
Source: crash
Binary: crash
Architecture: source amd64
Version: 5.1.4-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.4-1) unstable; urgency=low
.
* New upstream version 5.1.4 (see
http://people.redhat.com/anderson/crash.changelog)
* Fix for RT kernels in which the schedule() function has become a wrapper
function that calls the __schedule() function, and where other functions
may call __schedule() directly. Without the patch, a warning message
indicating "crash: cannot determing thread return address" is displayed
during invocation on x86_64 machines, and backtraces of blocked tasks may
have missing or invalid frames.
* Fix for running against live x86 kernels that were configured with
CONFIG_PHYSICAL_START containing a value that is greater than its
CONFIG_PHYSICAL_ALIGN value, and where the first symbol listed by
/proc/kallsyms is not "_text". Without the patch, the crash session fails
during invocation with the error message "crash: vmlinux and /dev/mem do
not match!" (or "/dev/crash" if applicable). As a work- around,
"/proc/kallsyms" can be entered on the command line, or the
"--reloc=<size>" option could be used, but the fix obviates that
requirement for live systems. It should be noted that dumpfiles of
kernels configured that way still do require that "/proc/kallsyms", or a
copy of it, or alternatively the "--reloc=<size>" option, to be entered on
the command line, as detailed in this changelog entry:
http://people.redhat.com/anderson/crash.changelog.html#4_0_4_5
* Unlike other extension modules, the "sial.so" module must be built within
a pre-built crash source tree because it uses header files from the
embedded gdb module. Therefore if a crash source tree is laid down,
entered, and "make extensions" is entered without first building the crash
utility, the build of sial.so build spews numerous error messages. To
avoid that, the sial.mk file has been modified to check whether the
embedded gdb build has been completed, and if it has not, just displays
"sial.so: build failed: requires the crash gdb-7.0 module".
* If an extension module does not have its own <module>.mk file, and is
built using the extensions/Makefile, then it will be compiled with the
-Wall flag.
* The "trace.so" extension module has been improved to use "trace.cmd" to
implement the "trace show" option, instead of maintaining a redundant code
base within the module itself. The trace-cmd command is better, mature,
and continually maintained. The new "trace show" option works like so:
(1) builds trace.dat from the core file and dumps it to /tmp. (2) execs
"trace-cmd report" upon the trace.dat file. (3) splices the output of
trace-cmd to the user and unlinks the temporary file.
* Updates to the "trace.so" extension module to extract trace_bprintk()
formats from a kernel core dump. It handles both the current format and a
new format that will be pushed out after the merge window has closed for
Linux 2.6.40. The new format is required for the kernel debugfs to export
the same bprintk data as well. This means that the trace.so extension
module will be able to extract more information than trace-cmd itself can
on a running kernel.
* Fix for the "gdb" command, or any command that resolves to a gdb command,
to not strip quotation marks from the input line. Without the patch, any
gdb command whose arguments contain quotation marks, (e.g. "printf") would
fail because they get incorrectly stripped from the input line.
* Fix for the "p" command if its symbolic argument is a "char *" that points
to a static data string containing an "%" character. Without the patch,
the command results in a segmentation violation.
* Fix for the "sys -c" option to display an error message if a known
sys_call_table entry is not a valid system call address. Without the
patch, the compromised system call entry is not displayed unless the crash
debug mode is set to 1 or greater. With the patch, the system call number
will be followed by an error message indicating "invalid sys_call_table
entry: <address> (<symbol-name>)". This change is only applicable on
architectures/kernels where the index of the sys_call_table array can be
confirmed by debuginfo data, i.e., is not a loose calculation based upon
the next kernel symbol.
* Print a warning message if there is any inconsistency between the kernel
version strings found in the vmlinux file vs. the dumpfile or live memory.
If a System.map file is used to correct the virtual addresses found in the
vmlinux file, the message is not displayed.
* Fix for "kmem -v", and all other commands that search through the kernel's
mapped virtual address list, in x86_64 kernel versions from 2.6.0 to
2.6.11. Those kernels contained a "vmlist" and a separate "mod_vmlist"
list header, both of which point to list of vm_structs that described each
contiguous block of mapped kernel memory. 2.6.12 and later x86_64 kernels
consolidated both lists onto the "vmlist". Without the patch, the list
headed by "mod_vmlist" was not searched.
* Clarify the "struct -l offset" option so that it does not imply that the
address argument is necessarily an embedded list_head pointer. The "-l
offset" option essentially provides the capability of the kernel's
container_of() macro, such that the address of an embedded data structure
can be used to display its containing data structure.
* Clarify the help page documentation for the "struct -l offset" option so
that it does not imply that the address argument is necessarily an
embedded list_head pointer. The "-l offset" option essentially provides
the capability of the kernel's container_of() macro, such that the address
of an embedded data structure can be used to display its containing data
structure.
Checksums-Sha1:
17b737a14a53c13ee19788cbf6922d5d4c7425b9 1017 crash_5.1.4-1.dsc
88dcb7e4d43c9c75759e3559cf20a6c3872db16b 24381886 crash_5.1.4.orig.tar.gz
e44d1c96154ed9afd6f78f2226984b50512dd94e 26292 crash_5.1.4-1.diff.gz
08f575c9b68efa05a12ea41920698c0d981f0edf 2424362 crash_5.1.4-1_amd64.deb
Checksums-Sha256:
c808a65c08f94f53b7697c72cc1b7ab6698a9a049793c5723b6e18097ea69c74 1017 crash_5.1.4-1.dsc
3ea737f818b486f60af36fad7bf43c644ba91900fe0086bddf66f10ffe8475de 24381886 crash_5.1.4.orig.tar.gz
10be1e3bcc572e289e3150a603dd640475a040a8a375c2b0d2e8499df68e9b99 26292 crash_5.1.4-1.diff.gz
31121d4cdcc6231f059a627d6f8dae9094187c0426b2cbc978f342cb831fc5a3 2424362 crash_5.1.4-1_amd64.deb
Files:
86fbc4c60dfcf813af7848b14b8d11bd 1017 utils optional crash_5.1.4-1.dsc
32311207c07b3e884a02f76b0091aa8e 24381886 utils optional crash_5.1.4.orig.tar.gz
61a4c2a4a60bbfe50f1555cd5beb5bc1 26292 utils optional crash_5.1.4-1.diff.gz
7fdb3a62a9a022567f82fa9f8fd4270b 2424362 utils optional crash_5.1.4-1_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iD8DBQFNlghSQOr9C+GfGI4RArrUAKC4OurKkTx2+vao37Rb25H/Tq953ACfVG/2
etbdNXd0BlB8EjxdxGlNfTE=
=Mqih
-----END PGP SIGNATURE-----
Accepted:
crash_5.1.4-1.diff.gz
to main/c/crash/crash_5.1.4-1.diff.gz
crash_5.1.4-1.dsc
to main/c/crash/crash_5.1.4-1.dsc
crash_5.1.4-1_amd64.deb
to main/c/crash/crash_5.1.4-1_amd64.deb
crash_5.1.4.orig.tar.gz
to main/c/crash/crash_5.1.4.orig.tar.gz
Reply to: