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 703991 - Crash when using -fstack-protector-strong
Crash when using -fstack-protector-strong
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: general
3.10.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2013-07-11 10:46 UTC by Vadim Rutkovsky
Modified: 2013-09-21 13:35 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Vadim Rutkovsky 2013-07-11 10:46:03 UTC 
Evo 3.9.4 in rawhide crashes on initial setup.

Steps:
1) Remove all existing data:
  rm -rf ~/.local/share/evolution ~/.cache/evolution ~/.config/evolution
  evolution --force-shutdown
2) Start Evolution

Stdout:
*** stack smashing detected ***: evolution terminated
======= Backtrace: =========
/lib64/libc.so.6[0x3d6d47898f]
/lib64/libc.so.6(__fortify_fail+0x37)[0x3d6d50ba97]
/lib64/libc.so.6(__fortify_fail+0x0)[0x3d6d50ba60]
/usr/lib64/evolution/3.10/modules/module-mail-config.so(+0x6bd5)[0x7f26ef3a4bd5]
/usr/lib64/evolution/3.10/libevolution-mail.so(e_mail_config_service_page_add_scratch_source+0x344)[0x7f26f730af64]
/usr/lib64/evolution/3.10/libevolution-mail.so(+0x46394)[0x7f26f72fd394]
/usr/lib64/evolution/3.10/modules/module-startup-wizard.so(+0x486b)[0x7f26f4c5086b]
/lib64/libgobject-2.0.so.0(+0x1592a)[0x7f271015992a]
/lib64/libgobject-2.0.so.0(g_object_new_valist+0x354)[0x7f271015bb64]
/lib64/libgobject-2.0.so.0(g_object_new+0xf1)[0x7f271015bf61]
/usr/lib64/evolution/3.10/modules/module-startup-wizard.so(+0x43ca)[0x7f26f4c503ca]
/lib64/libgobject-2.0.so.0(g_closure_invoke+0x138)[0x7f27101543a8]
/lib64/libgobject-2.0.so.0(+0x22f4d)[0x7f2710166f4d]
/lib64/libgobject-2.0.so.0(g_signal_emit_valist+0xeab)[0x7f271016f11b]
/lib64/libgobject-2.0.so.0(g_signal_emit+0x8f)[0x7f271016f3bf]
evolution(main+0x527)[0x404197]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x3d6d421fa5]
evolution[0x4046a9]

Gdb trace:

+ Trace 232222

Thread 1 (Thread 0x7ffff3194a40 (LWP 2760))

  • #0 __GI_raise
    at ../nptl/sysdeps/unix/sysv/linux/raise.c line 56
  • #1 __GI_abort
    at abort.c line 89
  • #2 __libc_message
    at ../sysdeps/posix/libc_fatal.c line 175
  • #3 __GI___fortify_fail
    at fortify_fail.c line 31
  • #4 __stack_chk_fail
    at stack_chk_fail.c line 28
  • #5 mail_config_smtp_backend_insert_widgets
    at e-mail-config-smtp-backend.c line 286
  • #6 e_mail_config_service_page_add_scratch_source
    at e-mail-config-service-page.c line 831
  • #7 mail_config_assistant_constructed
    at e-mail-config-assistant.c line 752
  • #8 startup_assistant_constructed
    at e-startup-assistant.c line 118
  • #9 g_object_new_internal
    from /lib64/libgobject-2.0.so.0
  • #10 g_object_new_valist
    from /lib64/libgobject-2.0.so.0
  • #11 g_object_new
    from /lib64/libgobject-2.0.so.0
  • #12 e_startup_assistant_new
    at e-startup-assistant.c line 240
  • #13 startup_wizard_new_assistant
    at evolution-startup-wizard.c line 98
  • #14 startup_wizard_run
    at evolution-startup-wizard.c line 173
  • #15 startup_wizard_load_accounts
    at evolution-startup-wizard.c line 274
  • #16 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #17 signal_emit_unlocked_R
    from /lib64/libgobject-2.0.so.0
  • #18 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #19 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #20 main
    at main.c line 682 

Versions:
evolution-3.9.4-1.fc20.x86_64
evolution-data-server-3.9.4-1.fc20.x86_64
glibc-2.17.90-3.fc20.x86_64
Comment 1 Matthew Barnes 2013-07-11 10:53:03 UTC 
Works fine here, and the code it's tripping over hasn't changed since March.
Comment 2 Yanko Kaneti 2013-07-11 13:42:34 UTC 
Testing here points to the rawhide change between -fstack-prtector -> -fstack-protector-strong
Comment 3 Milan Crha 2013-07-12 09:47:18 UTC 
Is this evolution unrelated then?
Comment 4 Josh Bressers 2013-07-12 13:42:06 UTC 
It's likely that stack protector strong is turning up a latent bug in Evolution. My group inside Red Hat pushed for this change, we're investigating and will update this bug with our findings.

Thanks.
Comment 5 Dhiru Kholia 2013-07-12 18:25:10 UTC 
The offending code line seems to be "modules/mail-config/e-mail-config-smtp-backend.c +242" which is,

g_object_get (G_OBJECT (settings), "port", &port, NULL);

Note that "port" is defined as "guint16 port" earlier.

After commenting this line out, evolution is able to launch (at least).