Crash should depend on binutils

Bug #251288 reported by Kevin Worth on 2008-07-23
36
This bug affects 4 people
Affects Status Importance Assigned to Milestone
crash (Debian)
Fix Released
Unknown
crash (Ubuntu)
Medium
Chris J Arges
Precise
Medium
Chris J Arges
Quantal
Medium
Chris J Arges
Raring
Medium
Chris J Arges

Bug Description

Binary package hint: crash

Crash seems to depend on the program "strings" (in binutils package) to match vmcore dumps to vmlinux kernels. If you try to run crash without binutils installed, it will fail saying the vmlinux image and dump do not match (along with an error further up reporting that "strings" is not found).

Crash should have binutils package added to its deps.

Sergey Svishchev (svs) on 2010-12-21
summary: - Crash fails to load if binutils is not installed
+ Crash should depend on binutils
Jonathan Davies (jpds) on 2011-10-12
Changed in crash (Ubuntu):
status: New → Confirmed
importance: Undecided → Medium
Changed in crash (Debian):
status: Unknown → New
Jonathan Davies (jpds) on 2012-02-13
tags: added: rls-mgr-p-tracking
Changed in crash (Debian):
status: New → Fix Released
Chris J Arges (arges) on 2013-01-04
Changed in crash (Ubuntu Raring):
status: Confirmed → In Progress
assignee: nobody → Chris J Arges (christopherarges)
Chris J Arges (arges) wrote :
Changed in crash (Ubuntu Precise):
assignee: nobody → Chris J Arges (christopherarges)
status: New → In Progress
Changed in crash (Ubuntu Quantal):
status: New → In Progress
Changed in crash (Ubuntu Precise):
importance: Undecided → Medium
Changed in crash (Ubuntu Quantal):
importance: Undecided → Medium
assignee: nobody → Chris J Arges (christopherarges)
Chris J Arges (arges) wrote :
Chris J Arges (arges) wrote :

The attachment "add_binutils_depends_precise.debdiff" of this bug report has been identified as being a patch in the form of a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. In the event that this is in fact not a patch you can resolve this situation by removing the tag 'patch' from the bug report and editing the attachment so that it is not flagged as a patch. Additionally, if you are member of the ubuntu-sponsors team please also unsubscribe the team from this bug report.

[This is an automated message performed by a Launchpad user owned by Brian Murray. Please contact him regarding any issues with the action taken in this bug report.]

tags: added: patch
Stefan Bader (smb) wrote :

I will start trying to get this change uploaded for Raring (replacing precise with raring, thoug ;)). And then move on after that gets up.

Launchpad Janitor (janitor) wrote :

This bug was fixed in the package crash - 6.1.0-1ubuntu2

---------------
crash (6.1.0-1ubuntu2) raring; urgency=low

  * Make crash depend on binutils. (LP: #251288)
    Crash uses the program strings to match vmlinux and cores.
 -- Chris J Arges <email address hidden> Fri, 04 Jan 2013 17:26:06 -0600

Changed in crash (Ubuntu Raring):
status: In Progress → Fix Released
Michael Terry (mterry) wrote :

I'll unsubscribe ubuntu-sponsors, since you seem to have things in hand, Chris.

Hello Kevin, or anyone else affected,

Accepted crash into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/crash/6.1.6-1ubuntu0.12.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in crash (Ubuntu Precise):
status: In Progress → Fix Committed
tags: added: verification-needed
Changed in crash (Ubuntu Quantal):
status: In Progress → Fix Committed
Adam Conrad (adconrad) wrote :

Hello Kevin, or anyone else affected,

Accepted crash into quantal-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/crash/6.1.6-1ubuntu0.12.10.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Louis Bouchard (louis) on 2013-08-13
tags: added: verification-done
removed: verification-needed
Launchpad Janitor (janitor) wrote :
Download full text (102.4 KiB)

This bug was fixed in the package crash - 6.1.6-1ubuntu0.12.04.1

---------------
crash (6.1.6-1ubuntu0.12.04.1) precise-proposed; urgency=low

  * Merge from Debian unstable (LP: #1064475). Remaining changes:
    - debian/rules: Always build extensions and package them.
    - debian/rules: Cleanup for extensions.
  * Dropped ubuntu changes:
    - SPU extension support.
  * debian/control: Add armhf to build architectures.

crash (6.1.6-1) unstable; urgency=low

  * New upstream version 6.1.6

  * Fix for a crash-6.1.5 regression that causes the "mount" command to fail
    on kernel versions prior to Linux 3.3. Without the patch, the command
    fails with the message "mount: invalid structure member offset:
    mount_mnt_devname".

crash (6.1.5-1) UNRELEASED; urgency=low

  * New upstream version 6.1.6

  * Fix for the ARM "irq" command. Without the patch, on 2.6.34 and later
    kernels configured with CONFIG_SPARSE_IRQ, the command fails with the
    error message "irq: cannot determine number of IRQs".

  * Fix for a segmentation violation generated during invocation while parsing
    a makedumpfile-created "flat-format" vmcore-incomplete file. Without the
    patch, the crash session would display the error message "crash: unable to
    seek dump file vmcore-incomplete", followed by a segmentation violation.

  * Fix for a segmentation violation generated by the "kmem -s" option when
    encountering a corrupted array_cache structure that contains a bogus
    "avail" count that is greater than the maximum legitimate limit value.
    Without the patch, the "kmem -s" command would print a warning message
    regarding the invalid array_cache, complete the command normally, and then
    generate a segmentation violation when freeing buffers used by the
    command.

  * Update to the "kmem -s" function to include the errors found in slab
    structures to the display of total errors found when the command
    completes. Without the patch, invalid list_head pointers, bad inuse
    counters, and bad s_mem pointers were not added to the total number of
    errors found.

  * Fix for "crash --osrelease <dumpfile>" and "crash --log <dumpfile>" when
    run on an ARM compressed kdump with a crash binary that was built with
    "make target=ARM" on an x86 or x86_64 host. Without the patch, if the
    compressed kdump header version is 4 or 5, "crash --osrelease" fails with
    the error message "crash: compressed kdump: cannot lseek dump vmcoreinfo"
    followed by "unknown", and "crash --log" fails with the error message
    "crash: <dumpfile>: no VMCOREINFO section".

  * Enhancement to the "swap" command to display the swap_info_struct address
    of each configured swap device. The output has been changed to display
    the address in the first column, and the variable-length device name has
    been moved to the last column.

  * Fix for the "kmem -[sS]" options on kernels that configured with both
    CONFIG_SLUB and CONFIG_NODES_SHIFT, and that are running on hardware that
    generates NUMA nodes that contain no memory. Without the patch, both
    command options fail immediately with the message "kmem: invalid kernel
    virtual ad...

Changed in crash (Ubuntu Precise):
status: Fix Committed → Fix Released
Launchpad Janitor (janitor) wrote :
Download full text (102.4 KiB)

This bug was fixed in the package crash - 6.1.6-1ubuntu0.12.10.1

---------------
crash (6.1.6-1ubuntu0.12.10.1) quantal-proposed; urgency=low

  * Merge from Debian unstable (LP: #1064475). Remaining changes:
    - debian/rules: Always build extensions and package them.
    - debian/rules: Cleanup for extensions.
  * Dropped ubuntu changes:
    - SPU extension support.
  * debian/control: Add armhf to build architectures.

crash (6.1.6-1) unstable; urgency=low

  * New upstream version 6.1.6

  * Fix for a crash-6.1.5 regression that causes the "mount" command to fail
    on kernel versions prior to Linux 3.3. Without the patch, the command
    fails with the message "mount: invalid structure member offset:
    mount_mnt_devname".

crash (6.1.5-1) UNRELEASED; urgency=low

  * New upstream version 6.1.6

  * Fix for the ARM "irq" command. Without the patch, on 2.6.34 and later
    kernels configured with CONFIG_SPARSE_IRQ, the command fails with the
    error message "irq: cannot determine number of IRQs".

  * Fix for a segmentation violation generated during invocation while parsing
    a makedumpfile-created "flat-format" vmcore-incomplete file. Without the
    patch, the crash session would display the error message "crash: unable to
    seek dump file vmcore-incomplete", followed by a segmentation violation.

  * Fix for a segmentation violation generated by the "kmem -s" option when
    encountering a corrupted array_cache structure that contains a bogus
    "avail" count that is greater than the maximum legitimate limit value.
    Without the patch, the "kmem -s" command would print a warning message
    regarding the invalid array_cache, complete the command normally, and then
    generate a segmentation violation when freeing buffers used by the
    command.

  * Update to the "kmem -s" function to include the errors found in slab
    structures to the display of total errors found when the command
    completes. Without the patch, invalid list_head pointers, bad inuse
    counters, and bad s_mem pointers were not added to the total number of
    errors found.

  * Fix for "crash --osrelease <dumpfile>" and "crash --log <dumpfile>" when
    run on an ARM compressed kdump with a crash binary that was built with
    "make target=ARM" on an x86 or x86_64 host. Without the patch, if the
    compressed kdump header version is 4 or 5, "crash --osrelease" fails with
    the error message "crash: compressed kdump: cannot lseek dump vmcoreinfo"
    followed by "unknown", and "crash --log" fails with the error message
    "crash: <dumpfile>: no VMCOREINFO section".

  * Enhancement to the "swap" command to display the swap_info_struct address
    of each configured swap device. The output has been changed to display
    the address in the first column, and the variable-length device name has
    been moved to the last column.

  * Fix for the "kmem -[sS]" options on kernels that configured with both
    CONFIG_SLUB and CONFIG_NODES_SHIFT, and that are running on hardware that
    generates NUMA nodes that contain no memory. Without the patch, both
    command options fail immediately with the message "kmem: invalid kernel
    virtual ad...

Changed in crash (Ubuntu Quantal):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.