cron crashed with SIGSEGV in __pthread_initialize_minimal_internal()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cron (Debian) |
Invalid
|
Undecided
|
Unassigned | ||
eglibc (Ubuntu) |
Fix Released
|
Medium
|
James Hunt | ||
libnih (Ubuntu) |
Fix Released
|
High
|
Steve Langasek |
Bug Description
Binary package hint: cron
I installed karmic in Virtualbox. I updated it. I upgraded to Lucid on 1-15-10. When I restarted after the upgrade, apport came up to report this bug.
ProblemType: Crash
Architecture: amd64
Date: Fri Jan 15 11:17:01 2010
Disassembly: 0x0: Cannot access memory at address 0x0
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/sbin/cron
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
Package: cron 3.0pl1-106ubuntu3
ProcCmdline: CRON
ProcEnviron: PATH=(custom, no user)
ProcVersionSign
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:
?? ()
__pthread_
_init () from /lib/libpthread
?? ()
?? () from /lib64/
Tags: lucid
Title: cron crashed with SIGSEGV in __pthread_
Uname: Linux 2.6.32-10-generic x86_64
UserGroups:
Changed in cron (Ubuntu): | |
status: | New → Confirmed |
tags: | added: precise qa-manual-testing |
Changed in libnih (Ubuntu): | |
importance: | Undecided → High |
assignee: | nobody → Steve Langasek (vorlon) |
status: | New → In Progress |
Changed in cron (Debian): | |
status: | New → Invalid |
Changed in eglibc (Ubuntu): | |
assignee: | nobody → James Hunt (jamesodhunt) |
StacktraceTop: initialize_ minimal_ internal () .so.0
?? ()
__pthread_
_init () from /lib/libpthread
?? ()
?? ()