cron crashed with SIGSEGV in _init()

[James Westby]

Binary package hint: cron

First boot in to lucid gave me this.

ProblemType: Crash
Architecture: i386
AssertionMessage: (ep\t
Date: Mon Feb 8 19:00:04 2010
Disassembly: 0x0: Cannot access memory at address 0x0
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/sbin/cron
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/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:

[Apport retracing service (apport)]

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

[MarcRandolph (mrand)]

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 518161, 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.