hald-probe-input crashed with SIGSEGV in free()

Bug #505769 reported by Eyad Salah
50
This bug affects 9 people
Affects Status Importance Assigned to Milestone
hal (Ubuntu)
Confirmed
High
Unassigned

Bug Description

Binary package hint: hal

Happened shortly after system startup

ProblemType: Crash
Architecture: amd64
Date: Mon Jan 11 09:12:50 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/lib/hal/hald-probe-input
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
NonfreeKernelModules: nvidia
Package: hal 0.5.14-0ubuntu2
ProcAttrCurrent: unconfined (enforce)
ProcCmdline: /usr/lib/hal/hald-probe-input
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.32-10.14-generic
SegvAnalysis:
 Segfault happened at: 0x7f1467dc8bd9 <free+25>: mov -0x8(%rdi),%rax
 PC (0x7f1467dc8bd9) ok
 source "-0x8(%rdi)" (0x00007ff8) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: hal
StacktraceTop:
 free () from /lib/libc.so.6
 dbus_error_free () from /lib/libdbus-1.so.3
 ?? ()
 __libc_start_main () from /lib/libc.so.6
 ?? ()
Tags: lucid
Title: hald-probe-input crashed with SIGSEGV in free()
Uname: Linux 2.6.32-10-generic x86_64
UserGroups: dialout

Revision history for this message
Eyad Salah (eyad-salah) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 *__GI___libc_free (mem=0x8000) at malloc.c:3709
 dbus_error_free (error=0x7fff5d596ec0)
 main (argc=<value optimized out>,

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 hal (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
visibility: private → public
Changed in hal (Ubuntu):
importance: Medium → High
status: New → Confirmed
Revision history for this message
Stefan Fleiter (stefan-fleiter) wrote :

This is still a bug in Lucid.

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.