lshw crashed with signal 7 in munmap()

Bug #1145306 reported by Steven Noonan
This bug report is a duplicate of:  Bug #653082: SIGBUS on panda board (armel). Edit Remove
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
lshw (Debian)
New
Unknown
lshw (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

All I needed to do to reproduce was run 'lshw' on a Samsung Chromebook.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: lshw 02.16-1
Uname: Linux 3.4.0-02511-g6efeff4 armv7l
ApportVersion: 2.9-0ubuntu2
Architecture: armhf
CrashCounter: 1
Date: Mon Mar 4 13:09:25 2013
ExecutablePath: /usr/bin/lshw
MarkForUpload: True
ProcCmdline: lshw -businfo
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 LANGUAGE=en_GB:en
 SHELL=/bin/bash
Signal: 7
SourcePackage: lshw
StacktraceTop:
 munmap () at ../sysdeps/unix/syscall-template.S:81
 ?? ()
 ?? ()
 ?? ()
 __libc_start_main (main=0xb5a1, argc=2, ubp_av=0x7eb34824, init=<optimised out>, fini=0x49d95, rtld_fini=0x76fbe295 <_dl_fini>, stack_end=0x7eb34824) at libc-start.c:260
Title: lshw crashed with signal 7 in munmap()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
---
ApportVersion: 2.9-0ubuntu2
Architecture: armhf
DistroRelease: Ubuntu 13.04
MarkForUpload: True
Package: lshw 02.16-1
PackageArchitecture: armhf
Tags: raring
Uname: Linux 3.4.0-02511-g6efeff4 armv7l
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: audio games staff sudo users video

Revision history for this message
Steven Noonan (steven-valvesoftware) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 <unavailable> in ?? ()
 PC not available
StacktraceSource: #0 <unavailable> in ?? ()
StacktraceTop: <unavailable> in ?? ()
ThreadStacktrace: PC not available

Changed in lshw (Ubuntu):
importance: Undecided → Medium
tags: removed: need-armhf-retrace
Revision history for this message
Steven Noonan (steven-valvesoftware) wrote : Dependencies.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Steven Noonan (steven-valvesoftware) wrote : ProcEnviron.txt

apport information

Revision history for this message
Steven Noonan (steven-valvesoftware) wrote :

For whatever reason, apport-collect doesn't want to generate DistroRelease, which is blocking my ability to apport-retrace

Changed in lshw (Ubuntu):
status: New → Invalid
Revision history for this message
Steven Noonan (steven-valvesoftware) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed, since the report is ill-formed. Perhaps the report data got
modified?

  need more than 1 value to unpack

If you encounter the crash again, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

Revision history for this message
Steven Noonan (steven-valvesoftware) wrote :

Oops, looks like apport's broken.

I'm just going to include a stack trace here via gdb, remove the need-armhf-retrace tag and call it a day. The ddeb on ddebs.ubuntu.com doesn't match the CRC for lshw (despite identical package versions):

warning: the debug information found in "/usr/lib/debug/usr/bin/lshw" does not match "/usr/bin/lshw" (CRC mismatch).

So I've built it locally (-O0 -ggdb):

(gdb) thread apply all backtrace full

Thread 1 (process 8826):
#0 0x76e8e0a8 in munmap () at ../sysdeps/unix/syscall-template.S:81
No locals.
#1 0x0002b244 in scan_dmi (n=...) at dmi.cc:1780
        buf = "\342\376O-~\206M\367\364\364\257\212s\211p\\\000\000\000"
        mmoffset = 4080
        efi = false
        fd = 7
        fp = 1015792
        mmp = 0x76fde000
        smmajver = 0 '\000'
        smminver = 0 '\000'
        dmimaj = 0
        dmimin = 0
#2 0x0001c84a in scan_system (system=...) at main.cc:62
        computer = {This = 0x95228}
        hostname = "exynos\000\000\000\360\355v\000\000\000\000\320\000\000\000<\274\006\000\354\365\377~\350\365\377~\330\365\377~\000\000\000\000\213\250\370v Q\t\000\030\366\377~\320\000\000\000X\366\377~\b\366\377~\000\000\000\000\000\000\000\000\000\360\377v\000\000\000"
#3 0x0000b8e0 in main (argc=1, argv=0x7efff794) at lshw.cc:225
        computer = {This = 0x950f0}
(gdb)

It's presumably breaking because there's no DMI info to get:

$ sudo ./dmidecode -u
# dmidecode 2.11
$

Changed in lshw (Ubuntu):
status: Invalid → New
Changed in lshw (Debian):
status: Unknown → New
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in lshw (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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