cron crashed with SIGSEGV in _init()

Bug #510093 reported by wxdf
This bug report is a duplicate of:  Bug #447080: 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

no idea why cron was started ;-(
I use Ubuntu 10.04 LTS - the Lucid Lynx.

ProblemType: Crash
Architecture: i386
Date: Wed Jan 20 13:55:03 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-17.54-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
Tags: lucid
Title: cron crashed with SIGSEGV in _init()
Uname: Linux 2.6.31-17-generic i686
UserGroups:

Revision history for this message
wxdf (hboehme90) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

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

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.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.