Message on startup "kerneloops crashed with SIGSEGV in _int_malloc()"
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| kerneloops (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
This happened subseqent to an upgrade of Trusty and a kerneloops crash dialog box came up after boot and login.
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: kerneloops-daemon 0.12+git2009021
ProcVersionSign
Uname: Linux 3.13.0-14-generic x86_64
NonfreeKernelMo
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
Date: Thu Mar 6 20:54:45 2014
ExecutablePath: /usr/sbin/
InstallationDate: Installed on 2014-02-17 (18 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
ProcCmdline: /usr/sbin/
ProcEnviron:
TERM=linux
PATH=(custom, no user)
SegvAnalysis:
Segfault happened at: 0x7f5f44e12231 <_int_malloc+2337>: mov %r13,(%rax,%r13,1)
PC (0x7f5f44e12231) ok
source "%r13" ok
destination "(%rax,%r13,1)" (0xa726f7273e7f260) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: kerneloops
StacktraceTop:
_int_malloc (av=0x7f5f45150760 <main_arena>, bytes=16000) at malloc.c:3740
__GI___libc_malloc (bytes=16000) at malloc.c:2891
?? ()
?? ()
?? () from /lib/x86_
Title: kerneloops crashed with SIGSEGV in _int_malloc()
UpgradeStatus: Upgraded to trusty on 2014-02-26 (9 days ago)
UserGroups:
| Andrew Ryan (boepie-gmail) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| information type: | Private → Public |
| tags: | removed: need-amd64-retrace |
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 #1287351, 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.