- Implemented a new "bt -F" flag as an extension of the "bt -f" flag, which dumps the contents of each stack frame in a backtrace; but similar to the output of "rd -S", if a stack entry can be expressed symbolically it will be displayed as "symbol+offset", or if a stack entry comes from a slab cache, the slab cache name will be displayed inside brackets. (anderson@xxxxxxxxxx) - Fix for the %install stanza in the crash.spec file to check for the existence of the sial.so extension module. Without the patch, when building the src.rpm with rpmbuild on a system without the bison and flex packages, the installation phase fails with the error messages "cp: cannot stat `extensions/sial.so': No such file or directory" and "error: Bad exit status from /var/tmp/rpm-tmp.ubJZfY (%install)". (anderson@xxxxxxxxxx) - Minor correction to the error message displayed by the "crash -x" command line option when the pre-loading of an extension module fails. Without the patch, the error message may be preceded with "foreach:" instead of "crash:" when running with dumpfiles in which no panic task could be ascertained. (anderson@xxxxxxxxxx) - Fix for the x86_64 "bt" and "bt -E" commands if the kdump-generated NMI interrupts a task that has just entered kernel space but has not changed the RSP stack pointer register from its user-space location to the kernel stack. Without the patch, the "bt" command follows the display of the exception frame on the NMI exception stack with the message "WARNING: possibly bogus exception frame", displays the error message "bt: cannot transition from exception stack to current process stack", and does not display the user-space exception frame; the "bt -E" command does not find and display the kernel-space exception frame generated by the NMI. (anderson@xxxxxxxxxx) - Fix for compiler warnings when building "net.c" with -O2. Without the patch, there are 6 messages that indicate "warning: dereferencing pointer '<arg>' does break strict-aliasing rules". (anderson@xxxxxxxxxx) - Fix for a compiler warning when building "gdb_interface.c" with -O2. Without the patch, there is 1 message that indicates "warning: dereferencing type-punned pointer will break strict-aliasing rules". (anderson@xxxxxxxxxx) - Fix for the x86 "bt" command if the crash occurs during the execution of a kernel module's init_module() function. Without the patch, the backtrace attempt would contain a stack frame with a "(null)" symbol name, display "bt: cannot resolve stack trace", dump the text symbols on the stack, and any possible exception frames. (anderson@xxxxxxxxxx) - Fix to support newer KVM dumpfile format generated by "virsh dump" that may contain "block" and "kvmclock" devices in the dumpfile header. Without the patch, the session fails with the error message "crash: <dumpfile>: initialization failed". (pbonzini@xxxxxxxxxx, anderson@xxxxxxxxxx) - Fix for "kmem -[sS]" command on 2.6.34 and later CONFIG_SLUB kernels, which changed the kmem_cache.cpu_slab[NR_CPUS] array to be a per-cpu offset value. Without the patch, the command fails with the message "kmem: cannot determine location of kmem_cache.cpu_slab page". (anderson@xxxxxxxxxx) - Modified the "kmem -p" output to show the "INDEX" column values with a hexadecimal value because the "page.index" member is typically a shared-use field that may also contain a pointer value. Without the patch, pointer values would be displayed as large negative decimal values. (anderson@xxxxxxxxxx) - Addressed compiler warnings generated by net.c when built with -O2. (anderson@xxxxxxxxxx) - Fix for the "kmem <address>" command if the kernel's free page lists are corrupt, or in a state of flux, and cannot be followed. Without the patch, the search for page usage in the various locations is aborted if the free page lists cannot be traversed. (anderson@xxxxxxxxxx) - Fix to read KVM dumpfiles generated by the "virsh dump" of a RHEL5 guest from a RHEL6 host, and to support dumpfile format changes that contain "apic" and "__rhel5" devices. Without the patch, the session may fail during initialization with a segmentation violation, or with the error message "crash: <dumpfile>: initialization failed". (pbonzini@xxxxxxxxxx) Download from: http://people.redhat.com/anderson -- Crash-utility mailing list Crash-utility@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/crash-utility
