🚀 go-pugleaf

I'm using gdbm (1.5) and occasionally one of my gdbm files manages to 
mangle its database. The problem is that while the data are accessible
via gdbm_fetch(), a lookup through gdbm_nextkey() terminates without
returning the whole file.

Needless to say, this happens only if the database is heavily used;
thus, scanning the database after every access won't work.
Also needless to say, any mangled database contains confidential
information, so I can't post or mail it. Also needless to say, the
way I'm using the database absolutely depends on firstkey/nextkey
finding every record.

However, I am able to use a debugger. ;-)  Any gdbm experts out there
who can help shed some light on this, point me at places to search for
the problem, etc.? All database access goes through one program, which
can be hacked to death if necessary.

-- 
Darth Vader!  Only you would be so bold!
               -- Princess Leia Organa
-- 
Matthias Urlichs  --  urlichs@smurf.sub.org -- urlichs@smurf.ira.uka.de   /(o\
Humboldtstrasse 7 -- 7500 Karlsruhe 1 -- Germany  --  +49-721-9612521     \o)/