kerneloops assert failure: *** glibc detected *** /usr/sbin/kerneloops: free(): invalid next size (normal): 0x099254a0 ***

[John Lenton]

this came up during an upgrade. I don't know what caused it.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: kerneloops-daemon 0.12+git20090217-3ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6
Uname: Linux 3.5.0-4-generic i686
ApportVersion: 2.4-0ubuntu2
Architecture: i386
AssertionMessage: *** glibc detected *** /usr/sbin/kerneloops: free(): invalid next size (normal): 0x099254a0 ***
Date: Wed Jul 18 18:18:22 2012
ExecutablePath: /usr/sbin/kerneloops
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release Candidate i386 (20100928.1)
ProcCmdline: /usr/sbin/kerneloops
ProcEnviron:
 LANGUAGE=en_US:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: kerneloops
StacktraceTop:
 __libc_message (do_abort=2, fmt=0xb75e83dc "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:201
 malloc_printerr (action=<optimized out>, str=<optimized out>, ptr=0x99254a0) at malloc.c:5007
 ?? ()
 ?? ()
 ?? ()
Title: kerneloops assert failure: *** glibc detected *** /usr/sbin/kerneloops: free(): invalid next size (normal): 0x099254a0 ***
UpgradeStatus: Upgraded to quantal on 2012-06-19 (29 days ago)
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:
 __libc_message (do_abort=2, fmt=0xb75e83dc "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:201
 malloc_printerr (action=<optimized out>, str=<optimized out>, ptr=0x99254a0) at malloc.c:5007
 extract_oops (buffer=buffer@entry=0x9924498 "<7>[146186.372911] icmpv6_send: acast source", buflen=<optimized out>, remove_syslog=160584864, remove_syslog@entry=0) at dmesg.c:357
 scan_dmesg (unused=unused@entry=0x0) at dmesg.c:368
 main (argc=1, argv=0xbfdac784) at kerneloops.c:192

[Brian Murray (brian-murray)]

I was able to recreate this by installing the new version of kerneloops which actually enables it, the previous version did not. However, a second attempt to start the kerneloops service, sudo service kerneloops start, did not cause a crash.

[Brian Murray (brian-murray)]

Well, I guess it really did crash just not right away.

[Launchpad Janitor (janitor)]

This bug was fixed in the package kerneloops - 0.12+git20090217-3ubuntu5

---------------
kerneloops (0.12+git20090217-3ubuntu5) trusty; urgency=medium

  [ Colin King ]
  * fix memleak and add alloc null pointer checks (LP: #1287109)
    - memleak of buffer c in writefunction()
    - null pointer checks in extract_oops() and scan_dmesg() (LP: #1026251)

  [ Brian Murray ]
  * fix null pointer check in fill_lineinfo() (LP: #1026300)
 -- Brian Murray <email address hidden> Wed, 05 Mar 2014 08:58:57 -0800