GNOME Bugzilla – Bug 304783
Crash of Evolution Exchange Storage
Last modified: 2005-05-20 15:28:05 UTC
Distribution: Red Hat Enterprise Linux WS release 4 (Nahant) Package: gnome-utils Severity: normal Version: GNOME2.8.0 2.2.0 Gnome-Distributor: Red Hat, Inc Synopsis: Crash of Evolution Exchange Storage Bugzilla-Product: gnome-utils Bugzilla-Component: gdict Bugzilla-Version: 2.2.0 BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: during lookup of a user name Steps to reproduce the crash: 1. CTRL-N to create a new mail message 2. KA-BOOM 3. Expected Results: should open up the create new mail message How often does this happen? 50% of the time. Additional Information: Here is the backtrace from my gdb of the evolution-exchange-server: evolution-exchange-storage: search.c:78: ldap_search_ext: Assertion `( (ld)->ld_options.ldo_valid == 0x2 )' failed. Program received signal SIGABRT, Aborted.
+ Trace 59911
Thread NaN (LWP 5836)
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-05-19 17:36 UTC ------- Unknown version 2.2.0 in product gnome-utils. Setting version to "2.2.x".
Thanks for the bug report; you appear to be the second one to get this crash and appear to have some good debugging symbols in the stack trace. Any chance you could also install the debuginfo package for ORBit2 as well and get another stack trace? *** This bug has been marked as a duplicate of 303067 ***
Sure, let me know what package to download and build. Please include any specific compilation switches to pass to the configure before doing the build. Regards, Wendell
Doesn't RedHat provide debuginfo packages for RHEL? I know that it does for Fedora (see http://live.gnome.org/GettingTraces/DistroSpecificInstructions and http://download.fedora.redhat.com/pub/fedora/linux/core/3/i386/debug/, for example), which allows a user to just install those packages and then cause the crash to happen again and get a new stack trace. Much easier than any of the alternatives. If you can't find any debuginfo package, then assuming you're currently using RHEL packages already, then you can just download the ORBit2 srpm and rebuild it (let me know if you haven't done that before and want instructions). Alternatively, if you want to build from source manually, you'd use the -g option to gcc, and turn of any optimizations (other than perhaps -O2). ORBit2 should be the only package you need, though you may need to install other development libraries to get it to compile (e.g. glib-devel and libIDL-devel) if you don't have them installed already.
I downloaded ORBit2 2.12.2 and built it from source using the standard install prefix (/usr/local). What packages should I rebuild in my EVO set (evolution-2.2.2, soup-2.2.3, gal-2.4.2, evolution-data-server 1.2.2, gtkhtml-3.6.2) I assume this just means re-running the configure script and using the following switches: --with-orbit-prefix=PFX Prefix where ORBIT is installed (optional) --with-orbit-exec-prefix=PFX Exec prefix where ORBIT is installed (optional) correct?
Well, considering that you're putting things in a different prefix, there may be a subset of the packages that would be fine, but I don't know which set that would be (I'm a bugsquad member, not Evo maintainer), so you may have to do every last one of them in order to make sure you've got it. (Personally, I think rebuilding the ORBit2 rpm, and then only installing the debuginfo rpm that is generated would be easier, but then again, you don't seem to have any problems installing manually from source...)