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 729997 - Segfault in `g_queue_peek_head_link()`
Segfault in `g_queue_peek_head_link()`
Status: RESOLVED DUPLICATE of bug 729546
Product: evolution
Classification: Applications
Component: Mailer
3.12.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2014-05-12 09:16 UTC by Paul Menzel
Modified: 2014-05-14 17:10 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
(gdb) t a a bt f (549.54 KB, text/plain)
2014-05-12 09:17 UTC, Paul Menzel 		Details

Description Paul Menzel 2014-05-12 09:16:44 UTC 
Evolution crashed with a segmentation fault (GLIB_DEBUG=fatal-warnings) and the backtrace below. Unfortunately my console log buffer was too small so the other messages written to the terminal are lost.

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x6cbcfb40 (LWP 14681)]
g_queue_peek_head_link (queue=queue@entry=0x14) at /build/glib2.0-f_gKLq/glib2.0-2.40.0/./glib/gqueue.c:579
579	/build/glib2.0-f_gKLq/glib2.0-2.40.0/./glib/gqueue.c: Datei oder Verzeichnis nicht gefunden.
Comment 1 Paul Menzel 2014-05-12 09:17:35 UTC 
Created attachment 276368 [details]
(gdb) t a a bt f

`GLIB_DEBUG=fatal-warnings`
Comment 2 Milan Crha 2014-05-13 07:16:54 UTC 
Please do not attach backtraces, paste them as a comment. bugzilla has features to identify duplicates and so on, which helps, not talking about easier searching when the backtrace is part of the comment.

*** This bug has been marked as a duplicate of bug 729546 ***
Comment 3 Paul Menzel 2014-05-14 17:10:47 UTC 
(In reply to comment #2)
> Please do not attach backtraces, paste them as a comment. bugzilla has features
> to identify duplicates and so on, which helps, not talking about easier
> searching when the backtrace is part of the comment.

Sure. The backtrace was so big though, that I was not allowed to commit the comment and therefore I chose to attach it.