kern.log:
Aug 30 00:19:24 HOSTNAME kernel: [ 800.660599] pinger[2907]: segfault at 0 ip 00007f285714b0aa sp 00007fffd8320a18 error 4 in libc-2.17.so[7f28570c3000+1bc000]
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: squid3 3.3.8-1ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
Uname: Linux 3.11.0-4-generic x86_64
ApportVersion: 2.12.1-0ubuntu2
Architecture: amd64
Date: Fri Aug 30 00:19:24 2013
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/squid3/pinger
ExecutableTimestamp: 1376468430
InstallationDate: Installed on 2013-04-21 (129 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130420)
MarkForUpload: True
ProcCmdline: (pinger)
ProcCwd: /
ProcEnviron:
TERM=linux
PATH=(custom, no user)
SegvAnalysis:
Segfault happened at: 0x7f285714b0aa <__strcmp_sse2+26>: movlpd (%rsi),%xmm2
PC (0x7f285714b0aa) 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=139811265774408, use_localtime=use_localtime@entry=1, leap_correct=leap_correct@entry=0x7fffd8320a90, leap_hit=leap_hit@entry=0x7fffd8320a80, tp=tp@entry=0x7f2857488e80 <_tmbuf>) at tzfile.c:796
__tz_convert (timer=0x7fffd8320ad0, use_localtime=1, tp=0x7f2857488e80 <_tmbuf>) at tzset.c:632
debugLogTime () at ../../src/debug.cc:537
_db_print (format=format@entry=0x7f2857bd6661 "%s\n") at ../../src/debug.cc:123
Debug::finishDebug () at ../../src/debug.cc:760
Title: pinger crashed with SIGSEGV in __tzfile_compute()
UpgradeStatus: Upgraded to saucy on 2013-06-08 (82 days ago)
UserGroups:
upstart.squid3.override: manual
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.