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

[Launchpad Bug Tracker]

This bug was fixed in the package eglibc - 2.15-0ubuntu7

---------------
eglibc (2.15-0ubuntu7) precise; urgency=low

  [ James Hunt ]
  * debian/debhelper.in/libc.preinst: Moved logic from postinst to
    prompt user for services to restart. We ask here to allow the
    problematic cron to be stopped in the preinst, but defer the restart of
    remaining services until postinst time (LP: #508083).

  [ Steve Langasek ]
  * debian/debhelper.in/libc.{pre,post}inst: drop special casing of upstart
    jobs when restarting, since the check was completely wrong anyway,
    depending on the no-longer-existent /lib/init/readlink.
  * Drop obsolete gdm upgrade handling code that only applies for upgrades
    from hardy to lucid.
  * Remove the /etc/ld.so.conf.d/i486-linux-gnu.conf conffile on upgrade on
    i386, since it's no longer shipped and we should give consistent results
    on upgrade and install; and add a Breaks on the three library packages
    in lucid that used this path.

  [ Adam Conrad ]
  * debian/patches/any/local-nscd-NO_MAPPING.diff: Apply patch from Jeff Law
    to clean up thread handling in __nscd_get_nl_timestamp and resolve a few
    random crashing issues with chromium-browser and ktorrent (LP: #929219)
  * debian/rules.d/debhelper.mk: Fix RTLD_SO replacement regex for sanity.
 -- Adam Conrad <adconrad at ubuntu.com>   Thu, 12 Apr 2012 00:18:08 -0600

** Changed in: eglibc (Ubuntu)
       Status: Triaged => Fix Released

-- 
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:
  Fix Released
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