pinger crashed with SIGSEGV in malloc_consolidate()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
squid3 (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
could this be related to net outage?
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: squid3 3.3.8-1ubuntu6.2
ProcVersionSign
Uname: Linux 3.13.0-44-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
Date: Tue Feb 3 08:41:13 2015
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2014-02-17 (351 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: 0x7f1f478c13d5 <malloc_
PC (0x7f1f478c13d5) ok
source "0x18(%rax)" (0x42219b550098) 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@
_int_free (av=0x7f1f47c01760 <main_arena>, p=<optimized out>, have_lock=0) at malloc.c:4057
std::basic_
?? ()
?? ()
Title: pinger crashed with SIGSEGV in malloc_
UpgradeStatus: Upgraded to trusty on 2014-05-23 (255 days ago)
UserGroups:
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.