upowerd crashed with SIGSEGV in free()

Bug #551912 reported by Jeroen T. Vermeulen
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
upower (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Binary package hint: upower

Reporting as separate bug in the hope that the included debug info will be useful.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: upower 0.9.1-1
ProcVersionSignature: Ubuntu 2.6.32-18.27-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-18-generic i686
NonfreeKernelModules: wl nvidia
Architecture: i386
CrashCounter: 1
Date: Mon Mar 29 18:42:13 2010
ExecutablePath: /usr/lib/upower/upowerd
ProcCmdline: /usr/lib/upower/upowerd
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0x289e81 <free+49>: mov 0x4(%edx),%eax
 PC (0x00289e81) ok
 source "0x4(%edx)" (0x000000b4) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: upower
StacktraceTop:
 free () from /lib/tls/i686/cmov/libc.so.6
 usb_destroy_configuration () from /lib/libusb-0.1.so.4
 usb_free_dev () from /lib/libusb-0.1.so.4
 usb_find_devices () from /lib/libusb-0.1.so.4
 ?? ()
Title: upowerd crashed with SIGSEGV in free()
UserGroups:

Revision history for this message
Jeroen T. Vermeulen (jtv) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 *__GI___libc_free (mem=0xb8) at malloc.c:3709
 usb_destroy_configuration (dev=0x9ec1038)
 usb_free_dev (dev=0x9ec1038) at ../usb.c:293
 usb_find_devices () at ../usb.c:121
 up_device_csr_init (csr=0x9ebf120) at up-device-csr.c:289

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in upower (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Steve Beattie (sbeattie)
visibility: private → public
Changed in upower (Ubuntu):
status: New → Confirmed
Revision history for this message
Alex Murray (alexmurray) wrote :

Looks like a dupe of bug #526895

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.