Date: Tue, 26 Apr 2011 15:17:52 +0100 From: David Woodhouse <dwmw2@infradead.org> To: Matthias Apitz <guru@unixarea.de> Cc: gnome@freebsd.org, evolution-list@gnome.org Subject: Re: [Evolution] evolution-2.32.1 (FreeBSD HEAD) && calendar not working Message-ID: <1303827472.6417.113.camel@macbook.infradead.org> In-Reply-To: <20110426135234.GA1336@sh4-5.1blu.de> References: <20110424181903.GA1129@tiny> <1303673639.6417.7.camel@macbook.infradead.org> <20110425142311.GA31595@sh4-5.1blu.de> <1303760086.6417.25.camel@macbook.infradead.org> <20110426063226.GA13844@sh4-5.1blu.de> <1303808818.6417.63.camel@macbook.infradead.org> <20110426120415.GA2913@sh4-5.1blu.de> <1303819852.6417.100.camel@macbook.infradead.org> <20110426122621.GB2913@sh4-5.1blu.de> <1303821491.6417.108.camel@macbook.infradead.org> <20110426135234.GA1336@sh4-5.1blu.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 2011-04-26 at 15:52 +0200, Matthias Apitz wrote: > Forget what I wrote about dbus and gnome-session-daemon; I tested this > in a SSH session to the VM and not in the desktop itself; I'm so stupid > sometime :-( Heh. Easily done ;) > Here is goes again: > Program received signal SIGSEGV, Segmentation fault. > [Switching to Thread 29804300 (LWP 100114/initial thread)] > 0x29dd2d60 in ?? () > (gdb) > (gdb) > (gdb) > (gdb) > (gdb) bt > #0 0x29dd2d60 in ?? () > #1 0x290b754b in g_hash_table_lookup () from > /usr/local/lib/libglib-2.0.so.0 > #2 0x29f33dd6 in e2k_autoconfig_lookup_option () > from > /usr/local/lib/evolution-data-server-1.2/extensions/libecalbackendexchange.so > #3 0x29f3564f in e2k_autoconfig_new () > from > /usr/local/lib/evolution-data-server-1.2/extensions/libecalbackendexchange.so > #4 0x29f520b0 in exchange_account_connect () > from > /usr/local/lib/evolution-data-server-1.2/extensions/libecalbackendexchange.so > #5 0x29f25368 in open_calendar () from > /usr/local/lib/evolution-data-server-1.2/extensions/libecalbackende OK, so evolution-exchange is broken and causing your calendar server to die with a SIGSEGV. Can you rebuild evo-exchange with '-g' so that we get debugging symbols in it? This *might* be a red herring; it might just be because you're still using evo-exchange 2.32.1 against eds 2.32.3. But I don't think so; nothing should have changed in the ABI. I strongly suspect this is the same problem you originally had. Let's get the current version of evo-exchange building, just to eliminate that possibility and in case it's already fixed there. Did you manage to work around your compiler bug by building with -O1 or -O0? -- dwmw2
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1303827472.6417.113.camel>