Ubuntu
cron package

cron crashed with SIGSEGV in _init()

Bug #506634 reported by Mathilda Young
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)
Confirmed
Medium
Unassigned

Bug Description

Binary package hint: cron

I am using Ubuntu netbook remix under virtual box and then I upgraded from 9.10 to 10.04.

ProblemType: Crash
Architecture: i386
Date: Tue Jan 12 14:17:03 2010
Disassembly: 0x0: Cannot access memory at address 0x0
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/sbin/cron
InstallationMedia: Ubuntu-Netbook-Remix 9.10 "Karmic Koala" - Release i386 (20091028.4)
Package: cron 3.0pl1-106ubuntu3
ProcCmdline: CRON
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.32-10.14-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 ubuntu-unr
Title: cron crashed with SIGSEGV in _init()
Uname: Linux 2.6.32-10-generic i686
UserGroups:

Revision history for this message
Mathilda Young (gtrsdk) 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=-1216010552,
 _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 : ThreadStacktrace.txt
Changed in cron (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
MarcRandolph (mrand)
visibility: private → public
Revision history for this message
MarcRandolph (mrand) wrote :

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.

Changed in cron (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.