Bug 332527 – evo 2.6 crash at startup with a glibc error "0x080f6b50"

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 332527 - evo 2.6 crash at startup with a glibc error "0x080f6b50"


Summary:	evo 2.6 crash at startup with a glibc error "0x080f6b50"


Status:	RESOLVED DUPLICATE of bug 331731

Product:	evolution
Classification:	Applications
Component:	Shell
Version:	2.6.x
Hardware:	Other All

Importance:	Normal critical
Target Milestone:	---
Assigned To:	Evolution Shell Maintainers Team
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-02-25 13:07 UTC by Eloi Primaux
Modified:	2013-09-13 00:55 UTC

See Also:
GNOME target:	---
GNOME version:	2.13/2.14

Description Eloi Primaux 2006-02-25 13:07:49 UTC

Steps to reproduce:
1. just launch evolution-2.6


Stack trace:
Backtrace was generated from '/usr/Gnome-2.14/bin/evolution-2.6'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1234548368 (LWP 24209)]
0xffffe410 in ?? ()

+ Trace 66500

Thread 1 (Thread -1234548368 (LWP 24209))

#0 ??
#1 ??
#2 ??
#3 ??
#4 __lll_mutex_lock_wait
from /lib/libc.so.6
#5 _L_mutex_lock_190
from /lib/libc.so.6
#6 ??
#7 ??
from /lib/libpthread.so.0
#8 ??
#9 _XFlushInt
from /usr/X11R6/lib/libX11.so.6
#10 __libc_fork
at fork.c line 92



Other information:
## System libraries
(LFS-6.1 based system)
glibc 2.3.4
Xorg 6.9.0
glib-2.0 2.10.0
libbonobo-2.0 2.13.1
evolution-data-server-1.6 1.5.91
CFLAGS=' -O3 -march=athlon-xp -msse -m3dnow

Comment 1 Eloi Primaux 2006-02-25 13:08:44 UTC

terminal output :
CalDAV Eplugin starting up ...
*** glibc detected *** double free or corruption (out): 0x080f6b50 ***

Comment 2 André Klapper 2006-02-25 14:16:33 UTC

eloi, is this reproducible? could also be a memory corruption :-/

Comment 3 Eloi Primaux 2006-02-25 14:56:25 UTC

For me, (i have only one computer) it's reproducible
i mean it always the same issue when i start evo

but i agree that it could be a memmory corruption but i have no clue of how to detect it.

however i also reported some days ago a similar bug with a 'glibc detected' but the differences come from the error report:
before my last report it was an 0x081ee3b0 (see bug 332314) and now it's an 0x080f6b50
i can't yet say more about it (i need to read some docs about how to track memmory corruption)

Regards

Comment 4 Karsten Bräckelmann 2006-02-25 15:23:51 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


Identical stacktrace as bug 332314, which is a duplicate of bug 331731.

*** This bug has been marked as a duplicate of 331731 ***

Comment 5 Karsten Bräckelmann 2006-02-25 15:33:50 UTC

Eloi, this indeed is the same crash. The differing "0x" string in the output is a memory address, which will be different almost every time. :)

Comment 6 Eloi Primaux 2006-02-25 16:00:48 UTC

ok thank you for your comment, now i will have more ideas about it

Best regards
Eloi Primaux