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 12:38:12 -0400 [thread overview]
Message-ID: <20140613163812.GA17879@redhat.com> (raw)
In-Reply-To: <539B24FA.8070800@gmx.de>
On Fri, Jun 13, 2014 at 06:21:14PM +0200, Toralf Förster wrote:
> > caveat: it needs you to rerun configure.sh each time you pull, which
> > kinda sucks. I suppose it'd be better if it somehow did all this stuff
> > from the Makefile. I'll look into fixing it sometime unless someone else beats
> > me to it, but it's not on my urgent list.
> >
> ok (althought now the version string is completely empty if git is not installed, eg. on virtual test machines)
Ok, Just pushed something out so it falls back to grepping the Makefile
if git isn't installed. Guess that case is useful if someone was
building from one of the snapshot tarballs.
> > > Done parsing arguments.
> > > Marking all syscalls as enabled.
> > > *** Error in `trinity': double free or corruption (!prev): 0x08208e78 ***
> >
> > I've been chasing a bunch of corruption bugs this last week or so, and
> > I think I've killed the worst of the bunch.
> >
> > Does -x mremap make this stop happening for you ?
> neither "-x mremap" nor "-x madvise" helped hhm
>
> If it would help a lot I could try to bisect trinity to that.
I have a feeling it'll land on one of the bigger changesets, but it
might be useful to narrow down.
Dave
next prev parent reply other threads:[~2014-06-13 16:38 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 [this message]
2014-06-13 17:14 ` Toralf Förster
2014-06-13 17:30 ` Dave Jones
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=20140613163812.GA17879@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).