pinger crashed with SIGSEGV in std::basic_ostringstream<char, std::char_traits<char>, std::allocator<char> >::~basic_ostringstream()

[Eric Detheridge]

Got this crash in 14.04 while using Synaptic to perform an upgrade. Have version 0.8.6 of squid-deb-proxy and squid-deb-proxy-client installed.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: squid3 3.3.8-1ubuntu6.2
ProcVersionSignature: Ubuntu 3.16.0-37.51~14.04.1-generic 3.16.7-ckt9
Uname: Linux 3.16.0-37-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.14.1-0ubuntu3.10
Architecture: amd64
Date: Wed May 20 07:35:01 2015
ExecutablePath: /usr/lib/squid3/pinger
InstallationDate: Installed on 2013-02-13 (827 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
ProcCmdline: (pinger)
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0x7fe446085845: cmp 0x18(%rax),%r12
 PC (0x7fe446085845) ok
 source "0x18(%rax)" (0x31a6d0650098) not located in a known VMA region (needed readable region)!
 destination "%r12" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: squid3
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 std::basic_ostringstream<char, std::char_traits<char>, std::allocator<char> >::~basic_ostringstream() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
 ?? ()
 ?? ()
Title: pinger crashed with SIGSEGV in std::basic_ostringstream<char, std::char_traits<char>, std::allocator<char> >::~basic_ostringstream()
UpgradeStatus: Upgraded to trusty on 2014-05-12 (374 days ago)
UserGroups:

[Apport retracing service (apport)]

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 #1214379, 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.