system-tools-backends assert failure: *** glibc detected *** /usr/sbin/system-tools-backends: munmap_chunk(): invalid pointer: 0x0804bffd ***

Bug #550115 reported by uvok
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
system-tools-backends (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: system-tools-backends

no further information available....

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: system-tools-backends 2.9.4-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-17-generic i686
Architecture: i386
AssertionMessage: *** glibc detected *** /usr/sbin/system-tools-backends: munmap_chunk(): invalid pointer: 0x0804bffd ***
Date: Sun Mar 28 10:44:56 2010
ExecutablePath: /usr/sbin/system-tools-backends
InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Alpha i386 (20100113)
ProcCmdline: /usr/sbin/system-tools-backends
ProcEnviron:

Signal: 6
SourcePackage: system-tools-backends
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/tls/i686/cmov/libc.so.6
 abort () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /lib/tls/i686/cmov/libc.so.6
Title: system-tools-backends assert failure: *** glibc detected *** /usr/sbin/system-tools-backends: munmap_chunk(): invalid pointer: 0x0804bffd ***
UserGroups:

Revision history for this message
uvok (uvok-deactivatedaccount) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __kernel_vsyscall ()
 *__GI_raise (sig=6)
 *__GI_abort () at abort.c:92
 __libc_message (do_abort=2,
 malloc_printerr (action=<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 system-tools-backends (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Milan Bouchet-Valat (nalimilan) wrote :

Thanks for the report. This bug is a duplicate of bug 534154, which is fixed upstream (not yet in Lucid). The trace is not the same, but the cause is.

visibility: private → public
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.