mandb crashed with SIGSEGV in _gdbm_alloc()

Bug #145490 reported by piti
20
Affects Status Importance Assigned to Milestone
man-db (Ubuntu)
Incomplete
Medium
Colin Watson

Bug Description

Binary package hint: man-db

This produces while booting (ubuntu-gutsy)
this is the new bug-report tool that makes me know there was a problem (expect I saw the boot time was sometime strangely long)

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Thu Sep 27 09:31:31 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/lib/man-db/mandb
NonfreeKernelModules: nvidia
Package: man-db 2.4.4-3
PackageArchitecture: amd64
ProcCmdline: /usr/bin/mandb --no-purge --quiet
ProcCwd: /usr/share/man
ProcEnviron:
 SHELL=/bin/sh
 PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
Signal: 11
SourcePackage: man-db
StacktraceTop:
 ?? () from /usr/lib/libgdbm.so.3
 _gdbm_alloc () from /usr/lib/libgdbm.so.3
 gdbm_store () from /usr/lib/libgdbm.so.3
 ?? ()
 ?? ()
Title: mandb crashed with SIGSEGV in _gdbm_alloc()
Uname: Linux ubuntu 2.6.22-12-generic #1 SMP Sun Sep 23 20:03:18 GMT 2007 x86_64 GNU/Linux
UserGroups:

Revision history for this message
piti (piti-pablo) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? () from /usr/lib/libgdbm.so.3
_gdbm_alloc () from /usr/lib/libgdbm.so.3
gdbm_store () from /usr/lib/libgdbm.so.3
dbstore (in=0x7fffefa7ff50, basename=0x695270 "") at db_store.c:186
store_descriptions (head=<value optimized out>, info=0x7fffefa7ff50, base_name=0x689604 "") at descriptions_store.c:90

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Revision history for this message
Colin Watson (cjwatson) wrote :

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.)

Changed in man-db:
assignee: nobody → kamion
status: New → Incomplete
Changed in man-db:
importance: Undecided → Medium
Revision history for this message
Colin Watson (cjwatson) wrote :

Hi,

Any progress on this? I can't do very much (except by accident) without the information I asked for.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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