[Bug 1216605] Re: mandb crashed with SIGSEGV in __GI_sigemptyset()

[Colin Watson]

** Package changed: man-db (Ubuntu) => libpipeline (Ubuntu)

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to libpipeline in Ubuntu.
https://bugs.launchpad.net/bugs/1216605

Title:
  mandb crashed with SIGSEGV in __GI_sigemptyset()

Status in “libpipeline” package in Ubuntu:
  New

Bug description:
  mandb crashed with SIGSEGV in __GI_sigemptyset()

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: man-db 2.6.5-2
  ProcVersionSignature: Ubuntu 3.11.0-3.8-generic 3.11.0-rc6
  Uname: Linux 3.11.0-3-generic x86_64
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: amd64
  Date: Sun Aug 25 18:31:44 2013
  ExecutablePath: /usr/bin/mandb
  InstallationDate: Installed on 2013-08-25 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130622)
  MarkForUpload: True
  ProcCmdline: /usr/bin/mandb -pq
  SegvAnalysis:
   Segfault happened at: 0x7fe49685da50 <__GI_sigemptyset+144>:	movb   $0x0,(%rdi)
   PC (0x7fe49685da50) ok
   source "$0x0" ok
   destination "(%rdi)" (0x000007a7) not located in a known VMA region (needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: man-db
  StacktraceTop:
   __GI_sigemptyset (set=0x7a7) at sigempty.c:33
   pipeline_start () from /usr/lib/x86_64-linux-gnu/libpipeline.so.1
   ?? ()
   ?? ()
   ?? ()
  Title: mandb crashed with SIGSEGV in __GI_sigemptyset()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libpipeline/+bug/1216605/+subscriptions