From: Dave Jones <davej@redhat.com>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: trinity@vger.kernel.org
Subject: Re: current trinity gives glibc errors
Date: Fri, 20 Dec 2013 14:27:39 -0500 [thread overview]
Message-ID: <20131220192739.GA13124@redhat.com> (raw)
In-Reply-To: <52B45985.6060806@gmx.de>
On Fri, Dec 20, 2013 at 03:51:49PM +0100, Toralf Förster wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> When I run latest trinity at a stable 32 Bit Gentoo Linux user mode linux image I do now get :
>
> trinity -q -N 10000 -C 2 -x mremap
>
> ...
>
> [child0:1763] init_module (128) returned ENOSYS, marking as inactive.
> [child0:1763] ipc (117) returned ENOSYS, marking as inactive.
> [main] Random reseed: 3211420801
> [child0:1765] ioperm (101) returned ENOSYS, marking as inactive.
> [child0:1765] set_robust_list (311) returned ENOSYS, marking as inactive.
> [child0:1765] move_pages (317) returned ENOSYS, marking as inactive.
> *** glibc detected *** trinity: double free or corruption (out): 0x085bc000 ***
> ======= Backtrace: =========
> /lib/libc.so.6(+0x76552)[0x400a0552]
> trinity[0x805930e]
> trinity[0x8052085]
> trinity[0x805508c]
> trinity[0x804af91]
> trinity[0x804ead5]
> trinity[0x804a605]
> /lib/libc.so.6(__libc_start_main+0xf5)[0x40046ad5]
> trinity[0x804ab15]
If you could narrow down which syscalls are causing this it would help a lot.
scripts/find.sh might give you some ideas.
Dave
next prev parent reply other threads:[~2013-12-20 19:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-20 14:51 current trinity gives glibc errors Toralf Förster
2013-12-20 19:27 ` Dave Jones [this message]
2013-12-20 20:23 ` Toralf Förster
2013-12-20 20:32 ` Toralf Förster
2013-12-20 20:50 ` Dave Jones
2013-12-20 20:59 ` Toralf Förster
2013-12-28 17:20 ` Toralf Förster
2014-02-21 21:28 ` Toralf Förster
2014-02-21 21:52 ` 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=20131220192739.GA13124@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.