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

Bug #550533 reported by joey.blacksmith
12
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

setting time zone...

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: Mon Mar 29 00:02:41 2010
ExecutablePath: /usr/sbin/system-tools-backends
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318)
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
joey.blacksmith (joey-blacksmith) wrote :
security vulnerability: yes → no
visibility: private → public
Revision history for this message
Milan Bouchet-Valat (nalimilan) wrote :

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

Revision history for this message
Milan Bouchet-Valat (nalimilan) wrote : Stacktrace.txt
Revision history for this message
Milan Bouchet-Valat (nalimilan) wrote : StacktraceSource.txt
Revision history for this message
Milan Bouchet-Valat (nalimilan) wrote : ThreadStacktrace.txt
Changed in system-tools-backends (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Milan Bouchet-Valat (nalimilan) wrote :

Woops! For some reason, apport-retrace removed the core dump even if it failed to retrace...

Revision history for this message
Milan Bouchet-Valat (nalimilan) wrote :

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

Revision history for this message
Milan Bouchet-Valat (nalimilan) wrote : Stacktrace.txt
Revision history for this message
Milan Bouchet-Valat (nalimilan) wrote : StacktraceSource.txt
Revision history for this message
Milan Bouchet-Valat (nalimilan) wrote : ThreadStacktrace.txt
Revision history for this message
Milan Bouchet-Valat (nalimilan) wrote :
Revision history for this message
Milan Bouchet-Valat (nalimilan) wrote :

Ah, I've finally managed to retrace the core dump on my box - I wanted to be sure I could check that crash before releasing 2.10.0 tonight. Hopefully, it seems to be a duplicate of bug 534154, which has a fix that will be released today too. If you want, you can install the test package I uploaded there to confirm it's really the same bug.

Sorry for the noise about the stacktraces, and please continue testing Lucid and reporting bugs!

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.