cron crashed with SIGSEGV in __kernel_vsyscall()

Bug #340417 reported by JoKerr
6
Affects Status Importance Assigned to Milestone
cron (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: cron

After partial update in a virtual machine.

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/sbin/cron
Package: cron 3.0pl1-105ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: /usr/sbin/cron
ProcEnviron:
 LC_CTYPE=
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
Signal: 11
SourcePackage: cron
StacktraceTop:
 __kernel_vsyscall ()
 nanosleep () from /lib/tls/i686/cmov/libc.so.6
 sleep () from /lib/tls/i686/cmov/libc.so.6
 ?? ()
 __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
Title: cron crashed with SIGSEGV in __kernel_vsyscall()
Uname: Linux 2.6.28-8-generic i686
UserGroups:

Revision history for this message
JoKerr (jo-kerr-free) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:__kernel_vsyscall ()
__nanosleep_nocancel () from /lib/tls/i686/cmov/libc.so.6
__sleep (seconds=0)
main (argc=51, argv=0x11f8352f) at ../cron.c:398

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in cron:
importance: Undecided → Medium
MarcRandolph (mrand)
visibility: private → public
Revision history for this message
Jamie Strandboge (jdstrand) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions: 1) Is this reproducible? 2) If so, what specific steps should we take to recreate this bug? This will help us to find and resolve the problem.

tags: added: jaunty
Revision history for this message
dino99 (9d9) wrote :

This version is outdated and no more supported

Changed in cron (Ubuntu):
status: New → Invalid
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.