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

Bug #509524 reported by Shane Fagan
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
hal (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: hal

Upgrade testing from hardy to lucid. I dont know the specifics of the problem but I have logs if it needs debugging.

ProblemType: Crash
Architecture: amd64
Date: Mon Jan 18 23:12:22 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/lib/hal/hald-probe-input
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: 0x7f152cee3c39 <posix_memalign+73>: mov %rax,%rdx
 PC (0x7f152cee3c39) ok
 source "%rax" ok
 destination "%rdx" ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: hal
StacktraceTop:
 posix_memalign () 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 posix_memalign()
Uname: Linux 2.6.32-10-generic x86_64
UserGroups:

Revision history for this message
Shane Fagan (shanepatrickfagan) wrote :
visibility: private → public
tags: added: hardy2lucid
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceSource:
 #0 0x00007f152cee3c39 in __posix_memalign (memptr=0x7fff85f42450,
 #1 0x00007f152d4130f8 in dbus_error_free (error=0x7fff85f42450)
 #2 0x0000000000401075 in main (argc=<value optimized out>,
StacktraceTop:
 __posix_memalign (memptr=0x7fff85f42450,
 dbus_error_free (error=0x7fff85f42450)
 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
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.