Packages not in Groups

crash-devel: crash utility for live systems; netdump, diskdump, kdump, LKCD or mcore dumpfiles

Name:crash-devel Vendor:StartCom Ltd., http://www.startcom.org
Version:4.0 License:GPL
Release:8.9.1.SEL5_3 URL:http://people.redhat.com/anderson
Summary
The core analysis suite is a self-contained tool that can be used to investigate either live systems, kernel core dumps created from the netdump, diskdump and kdump packages from Red Hat Linux, the mcore kernel patch offered by Mission Critical Linux, or the LKCD kernel patch.

Arch: x86_64

Download:crash-devel-4.0-8.9.1.SEL5_3.x86_64.rpm
Build Date:Tue Sep 8 22:39:31 2009
Packager:Anatoly Metetes <anatolym@startcom.org>
Size:139 KiB

Changelog

* Wed Sep 9 01:00:00 2009 Anatoly Metetes <anatolym{%}startcom{*}org>
- Rebuild for StartCom Linux 5.0.x
* Fri Jun 12 01:00:00 2009 Dave Anderson <anderson{%}redhat{*}com> - 4.0-8.9.1.el5
- Fix for running "foreach bt" on a live system, where a backtrace that
  is attempted on a task that no longer exists may cause a segmentation
  violation due to the use of stale/invalid kernel stack pointer.
- Resolves: rhbz#504796
* Sat Apr 18 01:00:00 2009 Dave Anderson <anderson{%}redhat{*}com> - 4.0-8.9.el5
- Re-based package to upstream version 4.0-8.9.
- Resolves: rhbz#494028
- Fix for nonsensical usage of the "set" command when running
  against the xen hypervisor binary.  If entered alone on the
  command line, the command would cause a segmentation violation,
  because there is no concept of a "context" in the xen hypervisor.
  In addition, more reasonable error messages are displayed if
  "set", "set -c <cpu>", "set -p", or "set <address>" are
  attempted when running against a xen hypervisor.
- Resolves: rhbz#462819
- Fix for "irq -d" option when run on x86_64 xen kernels.  Without the
  patch it would indicate: "irq: invalid structure size: gate_struct"
  and dump a stack trace leading to x86_64_display_idt_table().  Now it
  will indicate that the -d option is not applicable.
- Resolves: rhbz#464116
- Fixes for the "bt" command when running against the xen hypervisor
  binary.  The "bt -o" option, and setting it to run by default with
  "bt -O", would fail with the vmlinux-specific error message "bt:
  invalid structure size: desc_struct" with a stack trace leading
  to read_idt_table(); with the patch it will display the generic
  error message "bt: -o option not supported or applicable on this
  architecture or kernel".  The "bt -e" or "bt -E" will also display
  the same error message, as opposed to the command usage message.
  Lastly, the "bt -R" option would cause a segmentation violation;
  it has been fixed to work as it was designed.
- Resolves: rhbz#464288
- Fix for the "bt" command when run on a xen hypervisor in which the
  backtrace leads to either "process_softirqs" or "page_fault".
  Without the patch, the backtrace indicates: "bt: cannot resolve stack
  trace", and then the recovery code terminates the command with the
  nonsensical error message: "bt: invalid structure size: task_struct".
- Resolves: rhbz#466724
- Fix for "bt -a" command when running against the xen hypervisor where
  the number of physical cpus outnumber the MAX_VIRT_CPUS value for the
  processor type.  Without the patch on such a system, "bt -a" would
  fail after displaying backtraces for the first 32 (MAX_VIRT_CPUS)
  pcpus with the the error message: "bt: invalid vcpu".  The patch also
  corrects the "vcpus" command output to show the vcpus associated with
  pcpus 32 through 63, and the "doms" command output to show the second
  idle domain associated with pcpus 32 through 63.
- Resolves: rhbz#471790
- Fix for the "bt" command when run on a xen hypervisor in which the
  backtrace leads to either "process_softirqs" or "page_fault".
  Without the patch, the backtrace indicates: "bt: cannot resolve stack
  trace", and then the recovery code terminates the command with the
  nonsensical error message: "bt: invalid structure size: task_struct".
- Resolves: rhbz#474712
- Fix for "mod -[sS]" command if the target module object filename
  contains both underscore and dash characters.  Without the patch
  the module load would fail with the error message: "mod: cannot
  find or load object file for <name> module".  Examples are
  the "aes_x86_64" module from the "aes-x86_64.ko" object file, and
  the "dm_region_hash" module from the "dm-region_hash.ko" object file.
- Resolves: rhbz#480136
- Changed the manner in which the "bt" command determines which PID 0
  swapper task was interrupted by an ia64 INIT or MCA exception.
  There is an existing ia64 INIT/MCA handler bug which incorrectly
  writes the pseudo task's command name in its comm[] name string
  such that the cpu number may not be part of the string.  If that
  happens without this patch, the "bt" command fails to make the link
  back to the interrupted task, and displays the error message:
  "bt: unwind: failed to locate return link (ip=0x0)!"
- Resolves: rhbz#487429
- 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. 
- 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).
- Resolves: rhbz#495586

Listing created by RepoView-0.5.1-1