cron crashed with SIGSEGV in _init()

Bug #515346 reported by Walter_Wittel
This bug report is a duplicate of:  Bug #518161: cron crashed with SIGSEGV in _init(). Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cron (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: cron

Didn't see this crash reported against 10.04 lucid. Apport notification appeared after first reboot after upgrade from fully patched jaunty.

ProblemType: Crash
Architecture: i386
AssertionMessage: 0\365\067\b
Date: Sun Jan 31 19:17:08 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.31-16.53-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.31-16-generic i686
UserGroups:

Revision history for this message
Walter_Wittel (wittelw) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

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=-1216706872,
 add_to_global (new=<value optimized out>) at dl-open.c:130

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in cron (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
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.