cron crashed with SIGSEGV in getutline_r()

Bug #676409 reported by hinkie
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cron (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: cron

Bug reported following system freeze, reported on reboot.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: cron 3.0pl1-106ubuntu5
ProcVersionSignature: Ubuntu 2.6.32-25.45-generic 2.6.32.21+drm33.7
Uname: Linux 2.6.32-25-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Wed Nov 17 20:39:01 2010
ExecutablePath: /usr/sbin/cron
InstallationMedia: Mythbuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427.1)
ProcCmdline: CRON
ProcEnviron: PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0x7f175f6bd299: lret $0xf66
 PC (0x7f175f6bd299) ok
 source "$0xf66" ok
 SP (0x7fff3e07d518) ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: cron
StacktraceTop:
 ?? () from /lib/libc.so.6
 ?? () from /lib/libc.so.6
 getutline_r () from /lib/libc.so.6
 getutline () from /lib/libc.so.6
 pam_modutil_getlogin () from /lib/libpam.so.0
Title: cron crashed with SIGSEGV in getutline_r()
UserGroups:

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

StacktraceTop:
 __strncmp_sse2 ()
 getutline_r_file (line=<value optimized out>,
 __getutline_r (line=0x7fff3e07d660,
 __getutline (line=0x7fff3e07d700) at getutline.c:39
 pam_modutil_getlogin (pamh=0xbf6ce0)

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-amd64-retrace
Victor Vargas (kamus)
visibility: private → public
Revision history for this message
hinkie (hinkie) wrote :

Did a system memtest, which showed a couple of errors on SIMM DDR1 (of 4) in 5th pass, after 15 mins. SIMM now replaced and no errors noted after an hour of memtest. System monitoring will continue and any more bugs caught will be notified. Memtest error can be reproduced here it that is desired however it may be the presumed memory issue may be the issue here?

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.