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 360017 - crash in Evolution: Changed into the junk fo...
crash in Evolution: Changed into the junk fo...
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: general
2.8.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
: 360001 360154 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-10-05 21:27 UTC by trond.myklebust
Modified: 2007-02-12 11:58 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Attachments
Fix up a parser overflow in function parse_value() (344 bytes, patch)
2006-10-09 14:17 UTC, trond.myklebust
accepted-commit_now Details | Review

Description trond.myklebust 2006-10-05 21:27:27 UTC
What were you doing when the application crashed?
Changed into the junk folder while starting up 'evolution'


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 171331584 vsize: 0 resident: 171331584 share: 0 rss: 32903168 rss_rlim: 0
CPU usage: start_time: 1160083535 rtime: 0 utime: 627 stime: 0 cutime:558 cstime: 0 timeout: 69 it_real_value: 0 frequency: 30

Backtrace was generated from '/usr/bin/evolution-2.8'

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1233262928 (LWP 14857)]
[New Thread -1365972064 (LWP 14920)]
[New Thread -1356571744 (LWP 14910)]
[New Thread -1348179040 (LWP 14909)]
[New Thread -1339786336 (LWP 14885)]
[New Thread -1301099616 (LWP 14884)]
[New Thread -1318278240 (LWP 14879)]
[New Thread -1309885536 (LWP 14878)]
[New Thread -1275516000 (LWP 14876)]
[New Thread -1292706912 (LWP 14874)]
[New Thread -1283908704 (LWP 14873)]
[New Thread -1267123296 (LWP 14871)]
[New Thread -1258730592 (LWP 14870)]
[New Thread -1249559648 (LWP 14869)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1233262928 (LWP 14857))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libc.so.6
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 874
  • #3 segv_redirect
    at main.c line 426
  • #4 <signal handler called>
  • #5 __kernel_vsyscall
  • #6 *__GI___poll
    from /lib/tls/i686/cmov/libc.so.6
  • #7 g_main_context_iterate
    at gmain.c line 2979
  • #8 IA__g_main_loop_run
    at gmain.c line 2881
  • #9 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #10 main
    at main.c line 615
  • #0 __kernel_vsyscall

Comment 1 Karsten Bräckelmann 2006-10-06 02:41:17 UTC
*** Bug 360001 has been marked as a duplicate of this bug. ***
Comment 2 trond.myklebust 2006-10-09 14:17:39 UTC
Created attachment 74358 [details] [review]
Fix up a parser overflow in function parse_value()

This patch fixes the crash for me, at the expense of a bunch of assertion
warnings from camel. Nevertheless, it would appear to be doing the correct
thing, as the warnings I was previously seeing about
'e-data-server-WARNING **: Error in parsing: Unexpected token encountered: 0'
are gone...
Comment 3 trond.myklebust 2006-10-09 17:47:42 UTC
Hmm... Another (related?) issue is that the 'junk' folders which were
triggering the crash are still acting bit quirky: instead of immediately
seeing the list of junk messages when I click on the folder, I am having
to select "show: All Messages" in the toolbar first before they appear. I'm
not aware of having any special filtering options set on those folders.

Oh well. At least it is no longer crashing whenever I do this (a definite improvement).
Comment 4 Kjartan Maraas 2007-01-25 16:36:09 UTC
Please someone review and commit this patch.
Comment 5 Kjartan Maraas 2007-01-25 16:45:54 UTC
*** Bug 360154 has been marked as a duplicate of this bug. ***
Comment 6 Jeffrey Stedfast 2007-01-25 16:56:04 UTC
the patch looks safe to apply

I wonder if perhaps the code generating the junk vfolder sexp is broken? perhaps that's why it's not showing them? also, might be why this esexp parser patch was needed in the first place? not sure...
Comment 7 André Klapper 2007-01-27 17:35:04 UTC
bug 360237 comes to my mind...
Comment 8 Srinivasa Ragavan 2007-02-12 11:40:01 UTC
As fejj, says the patch is safe to commit.
Comment 9 Kjartan Maraas 2007-02-12 11:58:38 UTC
Commited to both branches.