[Bug 508083] Re: cron crashed with SIGSEGV in __pthread_initialize_minimal_internal()

[Eduard Grebe]

Seeing this crash in Precise (upgraded from Oneiric).

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

Title:
  cron crashed with SIGSEGV in __pthread_initialize_minimal_internal()

Status in “eglibc” package in Ubuntu:
  Triaged
Status in “libnih” package in Ubuntu:
  Fix Released
Status in “cron” package in Debian:
  Invalid

Bug description:
  Binary package hint: cron

  I installed karmic in Virtualbox. I updated it. I upgraded to Lucid on
  1-15-10. When I restarted after the upgrade, apport came up to report
  this bug.

  ProblemType: Crash
  Architecture: amd64
  Date: Fri Jan 15 11:17:01 2010
  Disassembly: 0x0:	Cannot access memory at address 0x0
  DistroRelease: Ubuntu 10.04
  ExecutablePath: /usr/sbin/cron
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  Package: cron 3.0pl1-106ubuntu3
  ProcCmdline: CRON
  ProcEnviron: PATH=(custom, no user)
  ProcVersionSignature: Ubuntu 2.6.32-10.14-generic
  SegvAnalysis:
   Segfault happened at: 0x0:	Cannot access memory at address 0x0
   PC (0x00000000) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: cron
  StacktraceTop:
   ?? ()
   __pthread_initialize_minimal_internal ()
   _init () from /lib/libpthread.so.0
   ?? ()
   ?? () from /lib64/ld-linux-x86-64.so.2
  Tags: lucid
  Title: cron crashed with SIGSEGV in __pthread_initialize_minimal_internal()
  Uname: Linux 2.6.32-10-generic x86_64
  UserGroups:

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