- Tentatively scheduled as the baseline version for the RHEL5.4 crash utility errata release. - Implemented a new "bt -g" option, which will display the backtraces of all threads in the targeted task's thread group. The thread group leader's backtrace will be displayed first, regardless of which task was the target of the "bt" command. (anderson@xxxxxxxxxx) - Implement support for the kdump "split-dumpfile" format, which can split /proc/vmcore into multiple dumpfiles as specified by the "makedumpfile --split" command option. It simply requires that all of the split dumpfile names be entered on the crash command line. (tindoh@xxxxxxxxxx) - Fix for "kmem -i", "kmem -n" and "kmem -p" on x86_64 CONFIG_SPARSEMEM and CONFIG_SPARSEMEM_EXTREME kernels that have MAX_PHYSMEM_BITS increased from 40 to 44. Without the patch, erroneous page-related data could be displayed depending upon the amount of physical memory contained by the target system. (anderson@xxxxxxxxxx) - For the architectures that support it, the "--machdep option=value" command line option has been modified to allow more than one machine- dependent argument. (anderson@xxxxxxxxxx) - The starting backtrace location of active, non-crashing, xen dom0 tasks are not available in kdump dumpfiles, nor is there anything that can be searched for in their respective stacks. Therefore, for those those tasks, the "bt" command will indicate: "bt: starting backtrace locations of the active (non-crashing) xen tasks cannot be determined: try -t or -T options". Without the patch, the backtrace would either be empty, or it would show an invalid backtrace starting at the last location where schedule() had been called. (anderson@xxxxxxxxxx) - Fix for potentially empty "bt -t" output, and for "bt -T" potentially dumping the text return addresses in the hard or soft IRQ stacks instead of the process stack. This could occur if the targeted task was the last task that used the hard or soft IRQ stack (x86 only). (anderson@xxxxxxxxxx) Download from: http://people.redhat.com/anderson -- Crash-utility mailing list Crash-utility@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/crash-utility
