Aaron Richton wrote:
test039 -b bdb, under watchmalloc so this in theory is The Actual Instruction:
I can tar up the testrun directory (or the entire source tree) if interested.
What OS and compiler version? Can you rule out hardware errors here? Compiler optimization bugs? This trace shows an actual SEGV in back-ldap, whereas your previous testrun directory doesn't show any faults.
Your previous one shows a successful Add of an entry (James A Jones 3) but subsequent references to it get No Such Object. That implies an index corruption, but the actual database files look ok. Also the offending entry is present in the final ldapsearch output, so really the DB seems consistent.
Any problem in back-bdb should have turned up in test008 first.