cron crashed with SIGSEGV in _init()

Bug #445018 reported by avinas
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

just happened after updates. Old scenic, 256 mb ram.

ProblemType: Crash
Architecture: i386
Date: Wed Oct 7 00:17:06 2009
Disassembly: 0xac3004: Cannot access memory at address 0xac3004
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/sbin/cron
Package: cron 3.0pl1-106ubuntu3
ProcCmdline: CRON
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.31-12.39-generic
SegvAnalysis:
 Segfault happened at: 0xac3004: Cannot access memory at address 0xac3004
 PC (0x00ac3004) ok
 Reason could not be automatically determined.
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.31-12-generic i686
UserGroups:

Revision history for this message
avinas (avinas17) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:?? ()
_init () from /lib/libpthread.so.0
_dl_debug_vdprintf (fd=<value optimized out>,
_dl_debug_vdprintf (fd=<value optimized out>,
_dl_close_worker (map=0xbf9203fc) at dl-close.c:189

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

Other bug subscribers

Remote bug watches

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