evolution-exchange-storage crash in e2k_global_catalog_lookup and ber_flush2

Yes, this is an instance of that bug. Compare that stack trace to the one in the Gnome bug report attached to the LP bug.

Can you please be clearer about what you mean by "hardy with updates"? Do you have the -proposed repository enabled? Also please provide the version of your libldap-2.4-2 package. I'm assuming you haven't tried any kind of package update since the core occurred. If you already have the fixed version of libldap I'll be very sad.

Thanks!

I had enabled hardy-proposed and upgraded libldap-2.4-2 and tested for bug #215904. At the time I tested it really seemed to help reduce crashing, but still crashed from time to time. After the update it crashed much less often, maybe 2 times per day rather than once every 30 min.

My libldap-2.4-2 is version 2.4.7-6ubuntu4.2.

I believe that is the updated version. Is that correct?

Still having these crashes once or twice per day. Likely I'm not the only one seeing these crashes. BTW, don't know if it matters, but I'm on x86_64.

To see whether you have the right stuff, look at the changelog file: /usr/share/doc/libldap-2.4-2/changelog.Debian.gz

You should see that the first entry in the changelog is either "openldap2.3 (2.4.7-6ubuntu4.2)" which contains this reference: "Fix ber_flush2 assertion error. (LP: #215904)"

Or, the first entry should be: "openldap2.3 (2.4.9-0ubuntu0.8.04)".

If it's not one of those two, please provide the version you DO have installed, and the date of the last entry in the changelog (the date comes at the end of each entry).

If it IS one of those two, have you re-verified that it's really the same bug by looking at the core dumps? Unfortunately Evo is not the most rock solid application in the world and I'm aware of at least one other crasher that exists in the version Ubuntu is currently publishing (I know because I posted the patch to fix it to the Gnome bugzilla, and they committed it but I haven't seen it show up in Ubuntu packages yet).

If the incidence of the crash changed dramatically, I wonder if you're not just seeing a different crash. Please post a stack trace of a recent crash, after you've verified you definitely have the fixed version of libldap.

I haven't crashed in a while. I believe the update finally got applied correctly. I must have done something wrong when trying to pull in the update from hardy-proposed.

Happened again. I'll attach a new backtrace.

Here's the top of my /usr/share/doc/libldap-2.4-2/changelog.Debian.gz file:

openldap2.3 (2.4.9-0ubuntu0.8.04) hardy-proposed; urgency=low

  * New upstream version: (LP: #237688)
    This verison fixes a number of bugs including syncrepl issues,
    assertion errors, and segmentation faults found in previous
    versions of openldap:
    http://www.openldap.org/software/release/changes.html.
    Dropped patches (included in the new upstream version):
     - debian/patches/entryCSN-backwards-compatibility (ITS #5348).
     - debian/patches/fix-notify-crasher.patch (ITS #5450).
     - debian/patches/libldap_r-link (ITS #4982).
     - debian/patches/sasl-cleartext-strncasecmp (ITS #5368).
     - debian/patches/slapd-tlsverifyclient-default (ITS #5360).
     - debian/patches/gnutls-ciphers patch (ITS #5341).
     - debian/patches/SECURITY_CVE-2008-0658.patch (#ITS 5358).
  * debian/patches/fix-syncrepl-oops: Fixes assertion when using syncrepl.
    (LP: #227178)
  * debian/patches/fix-assertion-io.patch,
    debian/patches/fix-dnpretty-assertion.patch:
    Add information about the related bugs these patches fix.

 -- Mathias Gug <email address hidden> Thu, 12 Jun 2008 19:33:42 -0400

So. I believe this bug is defiantly not a duplicate of #215904.

I've looked at the code and there's something that puzzles me and that's how sb_debug_write is in the stack trace 6 times like it is recursively calling itself. Is this what his happening in the macro LBER_SBIOD_WRITE_NEXT()?

I agree, this is not a duplicate. Although the stack trace is similar, that bug dies in the assert() showing an invalid sockbuf while this one gets past there and dies in the write somewhere. Plus, this appears to be failing with a SIGPIPE, which means some kind of unexpected pipe failure. I think this might need to be reported with openldap.

Which version of libldap are you using?

Thanks
chuck

libldap-2.4-2 2.4.9-0ubuntu0.8.04 from hardy updates.

I realize now that gdb was catching SIGPIPE before evolution had a chance to handle it. I've changed how I start gdb to ignore SIGPIPE. I will file a different bug if I uncover the real problem. This bug is invalid.