[Bug 1304261] Re: mandb crashed with SIGSEGV in gdbm_close

[Colin Watson]

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
Foundations Bugs, which is subscribed to man-db in Ubuntu.
https://bugs.launchpad.net/bugs/1304261

Title:
  mandb crashed with SIGSEGV in gdbm_close

Status in “man-db” package in Ubuntu:
  Triaged

Bug description:
  Maybe this is a dulpicate but Im not sure.
  L14.04 all updates installed

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: man-db 2.6.6-1
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic x86_64
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Tue Apr  8 10:30:45 2014
  ExecutablePath: /usr/bin/mandb
  InstallationDate: Installed on 2014-04-03 (4 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140401)
  ProcCmdline: /usr/bin/mandb -pq
  SegvAnalysis: Skipped: missing required field "Disassembly"
  Signal: 11
  SourcePackage: man-db
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/man-db/+bug/1304261/+subscriptions