I can't be absolutely sure why this is happening, because allocation
crashes like this often show up somewhere after the point where things
started to go wrong. However, the way man-db keeps track of its
database handle is asking for trouble: it's all done by way of a big
global variable, which might be OK if it were always zeroed after
closing but it isn't, so there are probably paths where it double-closes
the handle and sometimes crashes. I think I'll rearrange all that to
use sensibly-scoped local variables instead, which should get rid of
this kind of bug.
** Changed in: man-db (Ubuntu)
Status: New => Triaged
** Changed in: man-db (Ubuntu)
Assignee: (unassigned) => Colin Watson (cjwatson)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304261
Title:
mandb crashed with SIGSEGV in gdbm_close
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/man-db/+bug/1304261/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
