cron crashed with SIGSEGV in _init()

[las]

Binary package hint: cron

apport said need to report

ProblemType: Crash
Architecture: i386
AssertionMessage: 8\265.\b
Date: Sun Feb 7 00:05:02 2010
Disassembly: 0x0: Cannot access memory at address 0x0
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/sbin/cron
NonfreeKernelModules: nvidia
Package: cron 3.0pl1-106ubuntu3
ProcCmdline: CRON
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.32-12.17-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:
 ?? ()
 _init () from /lib/tls/i686/cmov/libpthread.so.0
 ?? () from /lib/ld-linux.so.2
 ?? () from /lib/ld-linux.so.2
 ?? () from /lib/ld-linux.so.2
Title: cron crashed with SIGSEGV in _init()
Uname: Linux 2.6.32-12-generic i686
UserGroups: adm admin audio cdrom dialout dip fax fuse lpadmin netdev plugdev root sambashare tape video

[Apport retracing service (apport)]

StacktraceTop:
 ?? ()
 _init () from /lib/tls/i686/cmov/libpthread.so.0
 ?? () at dl-error.c:191 from /lib/ld-linux.so.2
 _dl_signal_error (errcode=-1217014072,
 add_to_global (new=<value optimized out>) at dl-open.c:130

[MarcRandolph (mrand)]

Might be related to Bug #447080, but if so, the crashes have transitioned from that exact stack to this stack.

[MarcRandolph (mrand)]

Moving to triaged since this (and the duplicates) appear to be a valid traces.