pinger crashed with SIGSEGV in malloc_consolidate()

Bug #1397013 reported by Marcos K
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
squid3 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

out of mem?

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: squid3 3.3.8-1ubuntu6.1
ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
Uname: Linux 3.13.0-40-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
Date: Thu Nov 27 10:39:26 2014
ExecutablePath: /usr/lib/squid3/pinger
InstallationDate: Installed on 2014-02-17 (283 days ago)
InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
ProcCmdline: (pinger)
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0x7fafea96f2c5 <malloc_consolidate+133>: cmp 0x18(%rax),%r12
 PC (0x7fafea96f2c5) ok
 source "0x18(%rax)" (0x1fa6d6780098) not located in a known VMA region (needed readable region)!
 destination "%r12" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: squid3
StacktraceTop:
 malloc_consolidate (av=av@entry=0x7fafeacaf760 <main_arena>) at malloc.c:4165
 _int_free (av=0x7fafeacaf760 <main_arena>, p=<optimized out>, have_lock=0) at malloc.c:4057
 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 malloc_consolidate()
UpgradeStatus: Upgraded to trusty on 2014-05-23 (187 days ago)
UserGroups:

Revision history for this message
Marcos K (g-ubuntu-com-y) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in squid3 (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

squid3 version 3.3.8-1ubuntu6.1 required, but 3.3.8-1ubuntu6.2 is available

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-amd64-retrace
information type: Private → Public
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.