Ubuntu
man-db package

mandb crashed with SIGSEGV in gdbm_close

Bug #1304261 reported by fdwsgds
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
man-db (Ubuntu)
Fix Released
Medium
Colin Watson

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:

Related branches

lp:debian/man-db
Revision history for this message
fdwsgds (mubtcez) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 malloc_consolidate (av=av@entry=0x7f1417226760 <main_arena>) at malloc.c:4149
 _int_free (av=0x7f1417226760 <main_arena>, p=<optimized out>, have_lock=0) at malloc.c:4057
 gdbm_close () from /tmp/apport_sandbox_NjKu0I/usr/lib/x86_64-linux-gnu/libgdbm.so.3
 man_gdbm_close (wrap=0x7f1419910b50) at ../../../libdb/db_gdbm.c:240
 update_db (manpath=manpath@entry=0x7f1419912ef0 "/usr/share/man", catpath=catpath@entry=0x7f1419911c70 "/var/cache/man") at ../../../src/check_mandirs.c:672

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in man-db (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Colin Watson (cjwatson)
summary: - error appeared when installing yumi
+ mandb crashed with SIGSEGV in gdbm_close
Revision history for this message
Colin Watson (cjwatson) wrote :

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):
assignee: nobody → Colin Watson (cjwatson)
status: New → Triaged
Colin Watson (cjwatson)
Changed in man-db (Ubuntu):
status: Triaged → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package man-db - 2.7.2-1

---------------
man-db (2.7.2-1) unstable; urgency=medium

  * New upstream release:
    - Stop storing the database handle in a global variable (LP: #1304261).

 -- Colin Watson <email address hidden> Sun, 16 Aug 2015 17:30:19 +0100

Changed in man-db (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.