All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Toralf Förster" <toralf.foerster@gmx.de>
To: Dave Jones <davej@redhat.com>
Cc: trinity@vger.kernel.org
Subject: Re: current trinity gives glibc errors
Date: Sat, 28 Dec 2013 18:20:05 +0100	[thread overview]
Message-ID: <52BF0845.8060006@gmx.de> (raw)
In-Reply-To: <20131220205003.GA14629@redhat.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 12/20/2013 09:50 PM, Dave Jones wrote:
> On Fri, Dec 20, 2013 at 09:32:31PM +0100, Toralf Förster wrote:
>  > -----BEGIN PGP SIGNED MESSAGE-----
>  > Hash: SHA256
>  > 
>  > On 12/20/2013 08:27 PM, Dave Jones wrote:
>  > > 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
>  > >> 
>  > It is this :
>  > 
>  > trinity -q -l off -N 1 -c move_pages
> 
> Are you running as root ?  Probably best to just -x it for now.
> 
> sanitise_move_pages could use rewriting tbh, to use the new maps structs.
> I'll look at doing that in the new year.
> 
> 	Dave
> 
> 
With latest git tree 1.1-946-g7f333fd I cannot blame a single syscall for emitting the glibc error. I tried it with this command line (as a common user) :
$> for sc in `trinity -L | grep entrypoint | grep -v AVOID | awk '{ print $3 }' | sort -u`; do echo $sc; trinity -q -c $sc -C2 -N 9999 2>&1 | grep -B 4 -A 4 libc; sleep 2; don


So, it is either a combination of 2 or more syscalls (and ofc ML might be a culprit too).

BTW, the tag "v1.3" seems to be a light weight tag, right ? Because git describe" still refers to v1.1-..."

- -- 
MfG/Sincerely
Toralf Förster
pgp finger print:1A37 6F99 4A9D 026F 13E2 4DCF C4EA CDDE 0076 E94E
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iF4EAREIAAYFAlK/CEQACgkQxOrN3gB26U4v8QD/d2vnlF6UiT/1+04p7b1uvqxS
zWYa1hm4gz5x8oX6/64A/00qgnL3NwgAkia61ENPPLe4pqzYONslgm8vjqby0Kjy
=7FS7
-----END PGP SIGNATURE-----

  parent reply	other threads:[~2013-12-28 17:20 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
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 [this message]
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=52BF0845.8060006@gmx.de \
    --to=toralf.foerster@gmx.de \
    --cc=davej@redhat.com \
    --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.