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 410733 - evolution crashed with SIGSEGV in strlen()
evolution crashed with SIGSEGV in strlen()
Status: RESOLVED DUPLICATE of bug 273386
Product: evolution
Classification: Applications
Component: Mailer
2.10.x (obsolete)
Other Linux
: High critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
: 453925 474535 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-02-22 09:49 UTC by Sebastien Bacher
Modified: 2013-09-13 00:52 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Sebastien Bacher 2007-02-22 09:49:00 UTC 
That bug has been opened on https://launchpad.net/bugs/86928

"Binary package hint: evolution

when viewing a photo inline from an IMAP server, evolution crashed.
...
Package: evolution 2.9.91-0ubuntu2
...
"

Debug backtrace for the crash:

+ Trace 112841

  • #0 strlen
    from /lib/tls/i686/cmov/libc.so.6
  • #0 strlen
    from /lib/tls/i686/cmov/libc.so.6
  • #1 emf_insert_cache
    at em-format.c line 110
  • #2 em_format_set_inline
    at em-format.c line 984
  • #3 efhd_attachment_show
    at em-format-html-display.c line 1427
  • #4 efhd_attachment_button_show
    at em-format-html-display.c line 1433
  • #5 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #6 IA__g_closure_invoke
    at gclosure.c line 490
  • #7 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #8 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #9 IA__g_signal_emit
    at gsignal.c line 2243
  • #10 IA__gtk_button_clicked
    at gtkbutton.c line 889 






Comment 1


James Olds





          2007-02-23 07:53:40 UTC
        



Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!







Comment 2


André Klapper





          2007-02-23 08:50:57 UTC
        



the trace already has debugging symbols :-)
james, as an easy hint: every person in bugzilla has a number of points listed after the name - the more points you see, the more knowledge the person has (at least that's what people say ;-) )






Comment 3


André Klapper





          2007-05-21 11:52:01 UTC
        



duplicate of bug 340165 which has been fixed?






Comment 4


André Klapper





          2007-06-21 10:18:30 UTC
        



duplicate of bug 273386?






Comment 5


Tobias Mueller





          2007-07-17 01:09:45 UTC
        



*** Bug 453925 has been marked as a duplicate of this bug. ***






Comment 6


Srinivasa Ragavan





          2007-08-08 07:44:34 UTC
        



Im sure that this is a dupe of 273386. Please reopen if we get a trace similar to this with version after 2.11.6 

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






Comment 7


Tobias Mueller





          2007-09-29 01:35:06 UTC
        



*** Bug 474535 has been marked as a duplicate of this bug. ***






Comment 8


Tobias Mueller





          2008-04-21 18:51:41 UTC
        



(In reply to comment #6)
> Please reopen if we get a trace similar to this with version after 2.11.6 
> 
Hm. Maybe bug 529236 is a regression? It's on 2.12.