Hmm, I don't see anything particularly wrong with the stacktrace; this
must be some kind of latent memory corruption.
Could you please install the 'valgrind' package and run:
sudo -u man valgrind /usr/bin/mandb --no-purge --quiet >mandb.valgrind
2>&1
... and attach the resulting mandb.valgrind to this bug?
(valgrind has some problems in Gutsy at the moment, so we may have to
wait until a bit later and go through this a few times before we get
decent results, unfortunately.)
** Visibility changed to: Public
** Changed in: man-db (Ubuntu)
Assignee: (unassigned) => Colin Watson (kamion)
Status: New => Incomplete
--
mandb crashed with SIGSEGV in _gdbm_alloc()
https://bugs.launchpad.net/bugs/145490
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
