pinger crashed with SIGSEGV in __tzfile_compute()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
squid3 (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
reporting as new though probably a dupe of #1214806, which i've marked as affecting me several times now. This way the files generated get uploaded. This is for Trusty, and every morning i come to the computer to find it waiting for me. (I've said to no longer report for this version though.)
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: squid3 3.3.8-1ubuntu6
ProcVersionSign
Uname: Linux 3.13.0-20-generic x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Sun Mar 30 17:31:46 2014
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2014-03-08 (22 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
ProcCmdline: (pinger)
ProcEnviron:
TERM=linux
PATH=(custom, no user)
SegvAnalysis:
Segfault happened at: 0x7f00adfe5f0a <__strcmp_sse2+26>: movlpd (%rsi),%xmm2
PC (0x7f00adfe5f0a) ok
source "(%rsi)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%xmm2" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: squid3
StacktraceTop:
__tzfile_compute (timer=1396197105, use_localtime=
__tz_convert (timer=
?? ()
?? ()
?? ()
Title: pinger crashed with SIGSEGV in __tzfile_compute()
UpgradeStatus: Upgraded to trusty on 2014-03-10 (20 days ago)
UserGroups:
mtime.conffile.
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1214806, so is being marked as such. 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. Please continue to report any other bugs you may find.