GNOME Bugzilla – Bug 361460
keying in users names in a new mail message
Last modified: 2007-09-20 19:41:09 UTC
Steps to reproduce: 1. open evo 2. click on new mail 3. enter a users name Stack trace: Memory status: size: 72224768 vsize: 0 resident: 72224768 share: 0 rss: 21303296 rss_rlim: 0 CPU usage: start_time: 1160574808 rtime: 0 utime: 78 stime: 0 cutime:68 cstime: 0 timeout: 10 it_real_value: 0 frequency: 0 Backtrace was generated from '/home/wendell/garnome/libexec/evolution-exchange' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1235446096 (LWP 5143)] [New Thread -1252869216 (LWP 5590)] [New Thread -1235743840 (LWP 5149)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 75823
Thread 2 (Thread -1252869216 (LWP 5590))
Other information:
Launchpad bug with a similar crash: https://launchpad.net/bugs/92841 "Binary package hint: evolution-exchange Using Evolution Exchange. Sent an email, chose an email address off the global address list. Then sent and crashed. ProblemType: Crash Architecture: i386 CrashCounter: 1 Date: Fri Mar 16 12:11:34 2007 Disassembly: 0x0: DistroRelease: Ubuntu 7.04 ExecutablePath: /usr/lib/evolution/2.10/evolution-exchange-storage Package: evolution-exchange 2.10.0-0ubuntu1 PackageArchitecture: i386 ProcCmdline: /usr/lib/evolution/2.10/evolution-exchange-storage --oaf-activate-iid=OAFIID:GNOME_Evolution_Exchange_Component_Factory:2.10 --oaf-ior-fd=29 ... .
+ Trace 120703
The valgrind log on http://bugzilla.gnome.org/show_bug.cgi?id=329251 show an error around those lines of code: "==3682== Invalid read of size 4 ==3682== at 0x8068DC2: ldap_op_finished (e-book-backend-gal.c:325) ==3682== by 0x806BABB: stop_book_view (e-book-backend-gal.c:1553) ==3682== by 0x4031ACB: e_book_backend_stop_book_view (e-book-backend.c:324) ==3682== by 0x40357A2: impl_GNOME_Evolution_Addressbook_BookView_stop (e-data-book-view.c:450) ==3682== by 0x40278C3: _ORBIT_skel_small_GNOME_Evolution_Addressbook_BookView_stop (Evolution-DataServer-Addressbook-common.c:40) ==3682== by 0x56D6855: ORBit_POAObject_invoke (poa.c:1145) ==3682== by 0x56DAD83: ORBit_OAObject_invoke (orbit-adaptor.c:336) ==3682== by 0x56C81B9: ORBit_small_invoke_adaptor (orbit-small.c:835) ==3682== by 0x56D6B4B: ORBit_POAObject_handle_request (poa.c:1354) ==3682== by 0x56D715A: ORBit_POAObject_invoke_incoming_request (poa.c:1422) ==3682== by 0x56C2747: giop_thread_queue_process (giop.c:774) ==3682== by 0x56C27F8: giop_request_handler_thread (giop.c:484) ==3682== Address 0x5F72F18 is 8 bytes inside a block of size 40 free'd ==3682== at 0x401BF57: free (vg_replace_malloc.c:235) ==3682== by 0x57AF9A1: g_free (gmem.c:172) ==3682== by 0x806B647: ldap_search_dtor (e-book-backend-gal.c:1430) ==3682== by 0x8068E95: ldap_op_finished (e-book-backend-gal.c:337) ==3682== by 0x806B5A1: ldap_search_handler (e-book-backend-gal.c:1408) ==3682== by 0x806B1D5: poll_ldap (e-book-backend-gal.c:1325) ==3682== by 0x57AAAE3: g_timeout_dispatch (gmain.c:3257) ==3682== by 0x57A8EC3: g_main_context_dispatch (gmain.c:1913) ==3682== by 0x57AC04B: g_main_context_iterate (gmain.c:2544) ==3682== by 0x57AC337: g_main_loop_run (gmain.c:2748) ==3682== by 0x561743D: bonobo_main (bonobo-main.c:312) ==3682== by 0x805A941: main (main.c:238)"
*** Bug 440557 has been marked as a duplicate of this bug. ***
*** Bug 460963 has been marked as a duplicate of this bug. ***
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 332979 ***