cron crashed with SIGSEGV in _init()

[Barkhat]

Binary package hint: cron

I'm sorry this happened yesterday and I do not remember what I was doing. Using 10 Lucid version alpha

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Fri Jan 15 17:09:01 2010
Disassembly: 0x0: Cannot access memory at address 0x0
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/sbin/cron
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20091127)
NonfreeKernelModules: nvidia
Package: cron 3.0pl1-106ubuntu3
ProcAttrCurrent: unconfined (enforce)
ProcCmdline: CRON
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.32-10.14-generic-pae
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
Tags: lucid
Title: cron crashed with SIGSEGV in _init()
Uname: Linux 2.6.32-10-generic-pae i686
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:
 ?? ()
 _init () from /lib/tls/i686/cmov/libpthread.so.0
 _dl_signal_error (errcode=-1219012920,
 _dl_signal_error (errcode=<value optimized out>,
 add_to_global (new=<value optimized out>) at dl-open.c:138

[MarcRandolph (mrand)]

Howdy, and thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported, so it is being marked as a duplicate. 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. Feel free to continue to report any other bugs you may find.