On Wednesday, 04 April 2007 at 10:00, Fabian Groffen wrote: > So Darwin was the last platform that Mutt still worked, that is not > crashed in the header cache code. Some inspection with otool and ldd > revealed that on Darwin Mutt was linked against db-4.5, while on Linux > and Solaris was linked against db-4.3. For reasons not important here, > a faulty symlink usr/lib/libdb-4.dylib was existing on Darwin and > pointing to libdb-4.5.dylib. After I "fixed" that, Mutt crashed as hard > on Darwin as on Solaris and Linux (because it was also linked against db > 4.3). > > A little peek in configure.ac revealed checks for Berkely DB don't look > for anything higher than 4.3, which I have installed on Solaris, Darwin > and Linux, next to versions 4.4 and 4.5. In the attached patch I simply > added support for db 4.5 and 4.4 like done for 4.3 and below. > > While the patch allows me to use Mutt on Solaris, Darwin and Linux, it > of course is just a workaround here. I believe db 4.5 and 4.4 should be > checked, but if 4.3 (and below?) are found and taken as supported then > the code shouldn't crash. Possible solutions are to either drop support > for <4.3 or fix it in some way. > > Anyway, I hope this is useful information somehow. I'll apply the patch (db is up to 4.5 already?), but I'd like to have some idea what's causing the crashes before revoking support for 4.3 and under. Presumably they used to work for someone. Can you provide any diagnostics? On the other hand, I'm tempted to pull db4 entirely, since it seems like the most troublesome of the database engines.
Attachment:
pgpWmW0efmZb9.pgp
Description: PGP signature