pinger crashed with SIGSEGV in __strftime_internal()

Bug #1213455 reported by James Page
46
This bug affects 11 people
Affects Status Importance Assigned to Milestone
Squid
Unknown
Unknown
squid3 (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Started crashing after recent upgrade on saucy - might be something apparmor related?

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: squid3 3.3.8-1ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
Uname: Linux 3.11.0-2-generic x86_64
ApportVersion: 2.12-0ubuntu3
Architecture: amd64
Date: Sat Aug 17 13:51:29 2013
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/squid3/pinger
InstallationDate: Installed on 2013-04-23 (116 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423)
MarkForUpload: True
ProcCmdline: (pinger)
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0x7f0d4a961fed <__strftime_internal+29>: mov 0x8(%rcx),%edx
 PC (0x7f0d4a961fed) ok
 source "0x8(%rcx)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: squid3
StacktraceTop:
 __strftime_internal (s=0x7f0d4b5c78a0 "2013/08/16 15:01:53", maxsize=127, format=0x7f0d4b3bd56d "%Y/%m/%d %H:%M:%S", tp=0x0, tzset_called=tzset_called@entry=0x7ffffaf20dff, loc=0x7f0d4ac6b040 <_nl_global_locale>) at strftime_l.c:507
 __GI___strftime_l (s=<optimised out>, maxsize=<optimised out>, format=<optimised out>, tp=<optimised out>, loc=<optimised out>) at strftime_l.c:485
 ?? ()
 ?? ()
 ?? ()
Title: pinger crashed with SIGSEGV in __strftime_internal()
UpgradeStatus: Upgraded to saucy on 2013-06-15 (62 days ago)
UserGroups:

upstart.squid3.override: manual

Revision history for this message
James Page (james-page) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __strftime_internal (s=0x7f0d4b5c78a0 <debugLogTime()::buf> "2013/08/16 15:01:53", maxsize=127, format=0x7f0d4b3bd56d "%Y/%m/%d %H:%M:%S", tp=0x0, tzset_called=tzset_called@entry=0x7ffffaf20dff, loc=0x7f0d4ac6b040 <_nl_global_locale>) at strftime_l.c:507
 __GI___strftime_l (s=<optimized out>, maxsize=<optimized out>, format=<optimized out>, tp=<optimized out>, loc=<optimized out>) at strftime_l.c:485
 debugLogTime () at ../../src/debug.cc:538
 _db_print (format=format@entry=0x7f0d4b3bd661 "%s\n") at ../../src/debug.cc:123
 Debug::finishDebug () at ../../src/debug.cc:760

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in squid3 (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
James Page (james-page) wrote :

This appears to happen on boot only - I'm also using squid-deb-proxy (squid3 is disabled).

information type: Private → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in squid3 (Ubuntu):
status: New → Confirmed
Revision history for this message
Amos Jeffries (yadi) wrote :

This is fixed in the squid package now available in Xenial.

Changed in squid3 (Ubuntu):
status: Confirmed → Fix Released
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.