Thanks. This database is corrupt; accessdb can't open it, and gdb indicates that the hash bucket storage is confused beyond words.
There are (at least) two bugs here. The first is that gdbm_store segfaults when trying to insert a new entry into this database, rather than exiting cleanly; I've created a new bug task for this. The second is that, at least before gdbm started segfaulting, mandb should have fallen back to creating the database from scratch. I'll see if I can at least address the latter bug.
The possible third bug is why the database became corrupt in the first place, but I doubt we can answer that now; it could have been filesystem corruption due to e.g. a power failure.
In the meantime, run 'sudo -u man mandb --create --quiet' and that should clear things up for you.
Thanks. This database is corrupt; accessdb can't open it, and gdb indicates that the hash bucket storage is confused beyond words.
There are (at least) two bugs here. The first is that gdbm_store segfaults when trying to insert a new entry into this database, rather than exiting cleanly; I've created a new bug task for this. The second is that, at least before gdbm started segfaulting, mandb should have fallen back to creating the database from scratch. I'll see if I can at least address the latter bug.
The possible third bug is why the database became corrupt in the first place, but I doubt we can answer that now; it could have been filesystem corruption due to e.g. a power failure.
In the meantime, run 'sudo -u man mandb --create --quiet' and that should clear things up for you.