strigidaemon assert failure: *** glibc detected *** /usr/bin/strigidaemon: free(): invalid next size (fast): 0xb41ea788 ***

Bug #455040 reported by David Svensson
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
strigi (Ubuntu)
New
Medium
Unassigned

Bug Description

Description: Ubuntu karmic (development branch)
Release: 9.10

strigi-client:
  Installed: 0.7.0-1
  Candidate: 0.7.0-1
  Version table:
 *** 0.7.0-1 0
        500 http://se.archive.ubuntu.com karmic/universe Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
Architecture: i386
AssertionMessage: *** glibc detected *** /usr/bin/strigidaemon: free(): invalid next size (fast): 0xb41ea788 ***
CrashCounter: 1
Date: Mon Oct 19 01:44:03 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/strigidaemon
Package: strigi-daemon 0.7.0-1
ProcCmdline: /usr/bin/strigidaemon
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
Signal: 6
SourcePackage: strigi
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: strigidaemon assert failure: *** glibc detected *** /usr/bin/strigidaemon: free(): invalid next size (fast): 0xb41ea788 ***
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin audio cdrom dialout lpadmin netdev plugdev pulse-access sambashare

Revision history for this message
David Svensson (davidsvensson) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

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 : ThreadStacktrace.txt (retraced)
Changed in strigi (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
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.