All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: trinity@vger.kernel.org
Subject: Re: Error in `trinity': free(): invalid next size (normal): 0x08683438 ***
Date: Mon, 22 Sep 2014 09:41:08 -0400	[thread overview]
Message-ID: <20140922134108.GB32379@redhat.com> (raw)
In-Reply-To: <541CA0B8.4060809@gmx.de>

On Fri, Sep 19, 2014 at 11:31:36PM +0200, Toralf Förster wrote:
 > After a rather longer time w/o any issue I saw today this at a 32 bit Gentoox86 Linux KVM guest w/ v1.4-611-g01c61fc :
 > 
 > ...
 > [child1:18922] <timed out>
 > [child1:18933] <timed out>
 > *** Error in `trinity': free(): invalid next size (normal): 0x08683438 ***
 > ======= Backtrace: =========
 > /lib/libc.so.6(+0x734ef)[0xb76064ef]
 > /lib/libc.so.6(+0x79992)[0xb760c992]
 > /lib/libc.so.6(+0x7aac1)[0xb760dac1]
 > trinity(output_syscall_prefix+0x1b5)[0x8054465]
 > trinity(child_random_syscalls+0x1ce)[0x805f52e]
 > trinity(child_process+0x7e)[0x8054f8e]
 > trinity(main_loop+0x1f9)[0x8059469]
 > trinity(main+0x254)[0x8053b94]
 > /lib/libc.so.6(__libc_start_main+0xf5)[0xb75afee5]
 > trinity[0x8054135]

No idea what happened here tbh.  My best guess is one of the prior
syscalls stomped on something.  I've got some work in progress to
fix some of this stuff up, which I'll land over the next couple weeks.

	Dave

      reply	other threads:[~2014-09-22 13:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-19 21:31 Error in `trinity': free(): invalid next size (normal): 0x08683438 *** Toralf Förster
2014-09-22 13:41 ` Dave Jones [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140922134108.GB32379@redhat.com \
    --to=davej@redhat.com \
    --cc=toralf.foerster@gmx.de \
    --cc=trinity@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.