cron crashed with SIGSEGV in __pthread_initialize_minimal_internal()

Bug #465594 reported by Nolan Harris
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cron (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: cron

Fresh upgrade from Jaunty to Karmic. preceding cron crash was KDE freezing, on reboot, log into GNOME. Then crash report icon shows up.

ProblemType: Crash
Architecture: amd64
Date: Fri Oct 30 07:48:26 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/sbin/cron
NonfreeKernelModules: nvidia
Package: cron 3.0pl1-106ubuntu3
ProcCmdline: /USR/SBIN/CRON
ProcEnviron:
 LC_CTYPE=
 PATH=(custom, no user)
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x7f656bc87061: and %al,(%rax)
 PC (0x7f656bc87061) ok
 source "%al" ok
 destination "(%rax)" (0x7f656be7a6e8) ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: cron
StacktraceTop:
 ?? () from /lib/libpam.so.0
 __pthread_initialize_minimal_internal ()
 _init () from /lib/libpthread.so.0
 ?? ()
 ?? () from /lib64/ld-linux-x86-64.so.2
Title: cron crashed with SIGSEGV in __pthread_initialize_minimal_internal()
Uname: Linux 2.6.31-14-generic x86_64
UserGroups: vboxusers

Revision history for this message
Nolan Harris (nolan-agrtek) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:?? ()
?? ()
?? ()
?? ()
?? ()

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:?? ()
?? ()
?? ()
?? ()
?? ()

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
MarcRandolph (mrand)
visibility: private → public
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.