cron crashed with SIGSEGV in __pthread_initialize_minimal_internal()

Bug #947728 reported by Joy Bhattacherjee
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cron (Ubuntu)
New
Undecided
Unassigned

Bug Description

I upgraded from Oneiric 11.10 to Precise 12.04.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: cron 3.0pl1-120ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
Uname: Linux 3.2.0-18-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 1.94-0ubuntu1
Architecture: i386
Date: Tue Mar 6 04:17:01 2012
Disassembly: => 0x4596: Cannot access memory at address 0x4596
ExecutablePath: /usr/sbin/cron
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcCmdline: CRON
ProcEnviron: PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0x4596: Cannot access memory at address 0x4596
 PC (0x00004596) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: cron
StacktraceTop:
 ?? ()
 __pthread_initialize_minimal_internal () from /lib/i386-linux-gnu/libpthread.so.0
 _init () from /lib/i386-linux-gnu/libpthread.so.0
 ?? () from /lib/ld-linux.so.2
 ?? ()
Title: cron crashed with SIGSEGV in __pthread_initialize_minimal_internal()
UpgradeStatus: Upgraded to precise on 2012-03-06 (0 days ago)
UserGroups:

Revision history for this message
Joy Bhattacherjee (joy-bhattacherjee) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 __pthread_initialize_minimal_internal () at nptl-init.c:406
 _init () from /tmp/tmp7MCHxV/lib/i386-linux-gnu/libpthread.so.0
 ?? () from /tmp/tmp7MCHxV/lib/ld-linux.so.2
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
tags: added: apport-failed-retrace
tags: removed: need-i386-retrace
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 508083, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

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.