From: Dave Jones <davej@redhat.com>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: trinity@vger.kernel.org
Subject: Re: trinity: lots of corrupted double-linked list errors when run on x32
Date: Tue, 11 Feb 2014 12:13:59 -0500 [thread overview]
Message-ID: <20140211171359.GA31222@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1402061142030.17478@vincent-weaver-1.um.maine.edu>
On Thu, Feb 06, 2014 at 11:45:49AM -0500, Vince Weaver wrote:
>
> I'm running trinity compiled for x32 (by adding -mx32 to the CFLAGS
> and -static in the LDFLGAS as for some reason my debian system with x32
> libs installed gives "FATAL: kernel too old" if I try to run the
> dynamically linked version).
>
> Anyway I think glibc is reporting these particular errors. Should I try
> tracking them down? Or is this normal when running trinity?
>
> Vince
>
> *** Error in `./trinity': corrupted double-linked list: 0x018c31f8 ***
> *** Error in `./trinity': corrupted double-linked list: 0x01a68038 ***
> *** Error in `./trinity': corrupted double-linked list: 0x0170a448 ***
> *** Error in `./trinity': corrupted double-linked list: 0x01a0cd08 ***
> *** Error in `./trinity': free(): invalid size: 0x01a150d0 ***
I've spotted a bunch of weird stuff lately, like core dumps in odd places (when run with -D)
(and gdb insisting it doesn't match the executable). I think it started when
I added the mmap lists, but I've not nailed down exactly what's failing yet.
I'm looking into it, but haven't got a good feel for what's going wrong.
Dave
prev parent reply other threads:[~2014-02-11 17:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-06 16:45 trinity: lots of corrupted double-linked list errors when run on x32 Vince Weaver
2014-02-11 17:13 ` 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=20140211171359.GA31222@redhat.com \
--to=davej@redhat.com \
--cc=trinity@vger.kernel.org \
--cc=vincent.weaver@maine.edu \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).