GNOME Bugzilla – Bug 360017
crash in Evolution: Changed into the junk fo...
Last modified: 2007-02-12 11:58:38 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 ()
+ Trace 74791
Thread 1 (Thread -1233262928 (LWP 14857))
*** Bug 360001 has been marked as a duplicate of this bug. ***
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...
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).
Please someone review and commit this patch.
*** Bug 360154 has been marked as a duplicate of this bug. ***
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...
bug 360237 comes to my mind...
As fejj, says the patch is safe to commit.
Commited to both branches.