GNOME Bugzilla – Bug 634084
ECal reports loaded state too early
Last modified: 2010-11-09 09:20:01 UTC
Moving this from a downstream bug report: https://bugzilla.redhat.com/show_bug.cgi?id=650160 abrt version: 1.1.13 architecture: x86_64 Attached file: backtrace cmdline: /usr/libexec/e-calendar-factory component: evolution-data-server crash_function: e_intervaltree_search executable: /usr/libexec/e-calendar-factory kernel: 2.6.35.6-48.fc14.x86_64 package: evolution-data-server-2.32.0-3.fc14 rating: 4 reason: Process /usr/libexec/e-calendar-factory was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1288960793 uid: 500 Core was generated by `/usr/libexec/e-calendar-factory'. Program terminated with signal 11, Segmentation fault.
+ Trace 224510
Thread 1 (Thread 10176)
Created attachment 174053 [details] [review] eds patch for evolution-data-server; I cannot reproduce this myself, but I see what's going on: a) when opening calendar asynchronously, the ECal reported the load state as 'loaded', though it wasn't yet, which caused b) b) the EIntervalTree has some checking on non-NULL 'tree', but the first thing in the public functions was to access its 'priv' member, which lead to the crash This patch is fixing both things.
Created commit 3e433f5 in eds master (2.91.3+) Created commit c6d844f in eds gnome-2-32 (2.32.1+)