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 334798 - evolution-exchange-storage crashes constantly
evolution-exchange-storage crashes constantly
Status: RESOLVED DUPLICATE of bug 320015
Product: Evolution Exchange
Classification: Deprecated
Component: Connector
unspecified
Other All
: Normal critical
: ---
Assigned To: Connector Maintainer
Ximian Connector QA
: 325758 331096 335590 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-03-16 19:18 UTC by Jason Martens
Modified: 2007-08-22 13:23 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description Jason Martens 2006-03-16 19:18:24 UTC
Steps to reproduce:
1. Create an exchange account
2. Use it
3. Evolution-exchange-storage will crash


Stack trace:
Debugging Information:

Backtrace was generated from '/usr/libexec/evolution-exchange-storage'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1233307968 (LWP 4659)]
[New Thread -1234728016 (LWP 4660)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1233307968 (LWP 4659))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/tls/i686/cmov/libc.so.6
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 soup_message_io_pause
    from /usr/lib/libsoup-2.2.so.8
  • #5 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #6 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #7 g_signal_stop_emission
    from /usr/lib/libgobject-2.0.so.0
  • #8 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #10 soup_socket_get_remote_address
    from /usr/lib/libsoup-2.2.so.8
  • #11 g_vasprintf
    from /usr/lib/libglib-2.0.so.0
  • #12 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #13 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #14 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #15 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #16 main
  • #0 __kernel_vsyscall




Other information:
When running Evolution with Exchange, the evolution-exchange-storage
process constantly crashes.  Sometimes right when Evolution is opened,
sometimes after a long period of use.

Please DO NOT file this as a duplicate of bug #318624, unless you
re-open that bug.

evolution                 2.6.0-0ubuntu1
evolution-data-server     1.6.0-0ubuntu1
evolution-exchange        2.6.0-0ubuntu1
evolution-plugins         2.6.0-0ubuntu1  
evolution-webcal          2.5.90-0ubuntu1
Comment 1 Sushma Rai 2006-03-17 04:51:29 UTC
looks like some libsoup issue.
Which is your libsoup version?

Assigning to Chenthill and moving to libsoup.
Comment 2 Jason Martens 2006-03-17 18:04:13 UTC
I've tested with libsoup2.2.91-ubuntu, and 2.2.7-2 (Debian).  
Comment 3 Sushma Rai 2006-03-23 04:49:01 UTC
*** Bug 335590 has been marked as a duplicate of this bug. ***
Comment 4 Sushma Rai 2006-03-23 04:50:45 UTC
Another similar bug
http://bugzilla.gnome.org/show_bug.cgi?id=322901
Comment 5 Sushma Rai 2006-03-23 04:52:13 UTC
*** Bug 331096 has been marked as a duplicate of this bug. ***
Comment 6 Sushma Rai 2006-03-23 04:53:17 UTC
*** Bug 325758 has been marked as a duplicate of this bug. ***
Comment 7 Daniel Holbach 2006-04-04 19:45:28 UTC
Another Ubuntu backtrace:

Backtrace was generated from '/usr/libexec/evolution-exchange-storage'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1233254720 (LWP 4950)]
[New Thread -1234674768 (LWP 4951)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1233254720 (LWP 4950))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libc.so.6
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 792
  • #3 <signal handler called>
  • #4 io_read
    at soup-message-io.c line 522
  • #5 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #6 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #7 signal_emit_unlocked_R
    from /usr/lib/libgobject-2.0.so.0
  • #8 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #10 socket_read_watch
    at soup-socket.c line 1069
  • #11 g_io_unix_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #12 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #13 g_main_context_iterate
    from /usr/lib/libglib-2.0.so.0
  • #14 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #15 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #16 main
  • #0 __kernel_vsyscall

Comment 8 Jason Martens 2006-04-27 20:07:07 UTC
Our exchange server was recently upgraded from Exchange 2000 to Exchange 2003, and I have been running for a week on the new server with no crashes.  This bug seems to be connected to Exchange 2000 somehow.
Comment 9 Dan Winship 2006-05-26 21:18:50 UTC
does this bug still happen for anyone else?
Comment 10 Ivan Brezina 2006-06-04 13:38:35 UTC
Hallo
I also suffer from this bug. I cannot use evolution for more than 5minutes.
Here are results of my investigation:

I have tested on gentoo
evolution 2.4, 2.6
evolution-exchange 2.4.2, 2.6.0
libsoup 2.2.7, 2.2.92
glib 2.6.5, 2.8.6 

1. This bug is probably related to specific Exchange 2000 instalations.
   Our exchange often resets TCP connections, do not ask me why,
   it just does. 
2. It is not related to evolution-exchange, problem is somewhere between
   libsoup and glib.
3. stack trace produced by bug-buddy is different from gdb.
4. in gdb I see similar backtraces

(gdb) thread 2
[Switching to thread 2 (Thread -1227699280 (LWP 10392))]#0  0x4771c375 in libgnomeui_module_info_get () from /usr/lib/libgnomeui-2.so.0
(gdb) bt
  • #0 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #1 g_main_context_poll
    at gmain.c line 2867
  • #2 g_main_context_iterate
    at gmain.c line 2560
  • #3 IA__g_main_loop_run
    at gmain.c line 2769
  • #4 link_io_thread_fn
    at linc.c line 365
  • #5 g_thread_create_proxy
    at gthread.c line 564
  • #6 start_thread
    from /lib/tls/libpthread.so.0
  • #7 clone
    from /lib/tls/libc.so.6
  • #0 IA__g_type_instance_get_private
    at gtype.c line 3543
  • #1 io_write
    at soup-message-io.c line 373
  • #2 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #3 IA__g_closure_invoke
    at gclosure.c line 492
  • #4 signal_emit_unlocked_R
    at gsignal.c line 2485
  • #5 IA__g_signal_emit_valist
    at gsignal.c line 2244
  • #6 IA__g_signal_emit
    at gsignal.c line 2288
  • #7 socket_write_watch
    at soup-socket.c line 1280
  • #8 g_io_unix_dispatch
    at giounix.c line 162
  • #9 g_main_dispatch
    at gmain.c line 1934
  • #10 IA__g_main_context_dispatch
    at gmain.c line 2484
  • #11 g_main_context_iterate
    at gmain.c line 2565
  • #12 IA__g_main_loop_run
    at gmain.c line 2769
  • #13 bonobo_main
    at bonobo-main.c line 395
  • #14 main
    at main.c line 238


5. SEGFAULT allways occurs in some function in soup-message-io.c like io_write
    Each of these functions contains code like this:
    static void io_write (SoupSocket *sock, SoupMessage *msg)
    {
        SoupMessagePrivate *priv = SOUP_MESSAGE_GET_PRIVATE (msg);
        SoupMessageIOData *io = priv->io_data;
    none of these functions checks value of priv.
    
when SEGFAULT occurs priv is allways NULL and msg is ALLWAYS corrupted same way
 (gdb) p priv
$74 = (SoupMessagePrivate *) 0x0
(gdb) p *msg
$73 = {parent = {g_type_instance = {g_class = 0xb70348d0}, ref_count = 3070445776, qdata = 0xaaaaaaaa},
  method = 0xaaaaaaaa <Address 0xaaaaaaaa out of bounds>, status_code = 2863311530, reason_phrase = 0xaaaaaaaa <Address 0xaaaaaaaa out of bounds>,
  request = {owner = 2863311530, body = 0xaaaaaaaa <Address 0xaaaaaaaa out of bounds>, length = 2863311530}, request_headers = 0xaaaaaaaa, response = {
    owner = 2863311530, body = 0xaaaaaaaa <Address 0xaaaaaaaa out of bounds>, length = 2863311530}, response_headers = 0xaaaaaaaa, status = 2863311530}

As you see, whole msg structure is overwritten with weird value 0xaaaaaaaa.
Everytime evolution-exchange crashes msg contains these values.

I tried to find this constant in sources of glib, evoluton-*, libsoup and
others, without any success. 

Ivan
Comment 11 Dan Winship 2006-11-03 16:35:47 UTC
As per a long-ago discussion with Parag and Harish, I'm moving the soup connector bugs to the Evolution Exchange product, because I have no way of reproducing these bugs myself, so if they stay filed against libsoup, they're never going to get fixed.
Comment 12 Lucky Wankhede 2007-08-22 13:10:34 UTC

*** This bug has been marked as a duplicate of 320015 ***
Comment 13 Veerapuram Varadhan 2007-08-22 13:23:39 UTC
Can anyone try with the svn trunk version of libsoup or GNOME 2.18 version of libsoup and report back the status?