trinity.vger.kernel.org archive mirror
 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': double free or corruption (!prev): 0x08208e78 ***
Date: Fri, 13 Jun 2014 13:30:04 -0400	[thread overview]
Message-ID: <20140613173004.GA21623@redhat.com> (raw)
In-Reply-To: <539B3168.6050300@gmx.de>

On Fri, Jun 13, 2014 at 07:14:16PM +0200, Toralf Förster wrote:
 
 > $ trinity --list | grep Enabled$ | grep -v AVOID | cut -f3 -d' ' | while read s; do echo; echo $s; trinity -q -q -q -c $s -N 20 -C 1; done    
 > 
 > with latest trinity git tee and latest kernel tree which exposed the syscall "modify_ldt":
 > 
 > 
 > modify_ldt
 > Trinity 1.5pre  Dave Jones <davej@redhat.com>
 > [init] Marking syscall modify_ldt (123) as to be enabled.
 > Done parsing arguments.
 > *** Error in `trinity': double free or corruption (top): 0x0815d870 ***
 > ======= Backtrace: =========
 > /lib/libc.so.6(+0x7a202)[0x400a3202]
 > /lib/libc.so.6(+0x7af80)[0x400a3f80]
 > trinity(mkcall+0x17a)[0x805b0ca]
 > trinity(child_process+0x95)[0x8054965]
 > trinity(main_loop+0x1e3)[0x80583f3]
 > trinity(main+0x252)[0x8053752]
 > /lib/libc.so.6(__libc_start_main+0xf5)[0x40045cc5]
 > trinity[0x8053cd5]

Fixed.

thanks,

	Dave

      reply	other threads:[~2014-06-13 17:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-12 21:04 *** Error in `trinity': double free or corruption (!prev): 0x08208e78 *** Toralf Förster
2014-06-12 22:06 ` Dave Jones
2014-06-13 16:21   ` Toralf Förster
2014-06-13 16:38     ` Dave Jones
2014-06-13 17:14       ` Toralf Förster
2014-06-13 17:30         ` 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=20140613173004.GA21623@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).