From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/9785 Path: news.gmane.org!not-for-mail From: Max Ruttenberg Newsgroups: gmane.linux.lib.musl.general Subject: Re: Libc-Test: Tests failing on Ubuntu VM Date: Wed, 30 Mar 2016 13:22:19 -0400 Message-ID: References: <20160330164737.GL9862@port70.net> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=089e0117605b5715ac052f47632b X-Trace: ger.gmane.org 1459358589 25487 80.91.229.3 (30 Mar 2016 17:23:09 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 30 Mar 2016 17:23:09 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-9798-gllmg-musl=m.gmane.org@lists.openwall.com Wed Mar 30 19:22:52 2016 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1alJpN-0000G2-Q1 for gllmg-musl@m.gmane.org; Wed, 30 Mar 2016 19:22:45 +0200 Original-Received: (qmail 15800 invoked by uid 550); 30 Mar 2016 17:22:43 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Original-Received: (qmail 15770 invoked from network); 30 Mar 2016 17:22:42 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=emutechnology-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to; bh=nHyjWTP3P12Z6p7D01g7yMcf76EGzH7vXFUADnOgctw=; b=DlMYu6leDRDNafUs1zDK47WaHEJSz+mvHy1JpwXVi/D0I2PVSBi9yslb4DfLBQ7+u0 /jGqUXvYfO73sV1xLVn4YiYKJE+0gLnfScIf8Iy9dlb4b554nZWTefd7S3q9RC1P2w+w Y3NKRWtnxfO6qIdWroglhPwxPgLGGNTFBqOMVbQpMkheS7r0rQH7pjOTbMMfcGtBPHG9 uX0eUvhMN/BKiExnaNcO6AJzlAYixM6l8JCQB+OnEemdPXnuATKryxmhEScdNbDFkikX XcaGq37YVPeV2EG2Qx/8tsOcVZ+VFWsWtwjjTpdRJ/GiT6pKzTroybKvcIBmqFWMIzAq zBJQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to; bh=nHyjWTP3P12Z6p7D01g7yMcf76EGzH7vXFUADnOgctw=; b=AwX/Jk4AFoNHko4ioLTQLHQAIhdxirxpYmMX+XaXiIdGehiVrD9EHTOozzDVBvrWTK olPK02zGJylAutpS6kgTw3xYoh5eM0ScbG+9E1Z6TSmdNgt6xBNxuHGfQMLN0sGKYIQk KoCzfB9eB4ZxOYGwB2DviGGp2XmWoG8vAGRG1JLCegf9YEFbTOoz1EYksQR2jkLyD2xa 6hjxOapBTjPmO1fS15ks46bV05I/8Pl8ZidVLNMGTlQOFqjd+eCgxnyjqjLBBB55MGu+ yu+qB6zFAHfp54gLZt8lM5bF08rA/kaAsWqpwXc9yywXQagKMk6RCFgHxUqY60LnmTqK rK1A== X-Gm-Message-State: AD7BkJJsVUNmhhfgq8a6B/1proXS0pGkBnftJU8aalJj1hTcxuv1A9HCN22vSkSKn/4jyRTpSTkkBZQNJpshqA== X-Received: by 10.60.177.134 with SMTP id cq6mr6051296oec.68.1459358539375; Wed, 30 Mar 2016 10:22:19 -0700 (PDT) In-Reply-To: <20160330164737.GL9862@port70.net> Xref: news.gmane.org gmane.linux.lib.musl.general:9785 Archived-At: --089e0117605b5715ac052f47632b Content-Type: text/plain; charset=UTF-8 Szabolcs, Thank you! That was helpful. I have a couple of tests that still fail in functional but they clearly state "64bit tests not implemented." I still have a bunch of tests that fail in regression though... Running a make like so: make CC='/path/to/musl/bin/musl-gcc -Wl,-dynamic-linker=/path/to/ > musl/lib/libc.so' > this is what my src/regression/REPORT file looks like: ****************************************************************************************************************************** src/regression/malloc-brk-fail.c:33: malloc did not fail with ENOMEM, got Operation not permitted FAIL ./src/regression/malloc-brk-fail-static.exe [status 1] src/regression/malloc-brk-fail.c:33: malloc did not fail with ENOMEM, got Operation not permitted FAIL ./src/regression/malloc-brk-fail.exe [status 1] src/regression/malloc-oom.c:16: expected ENOMEM, got Operation not permitted FAIL ./src/regression/malloc-oom-static.exe [status 1] src/regression/malloc-oom.c:16: expected ENOMEM, got Operation not permitted FAIL ./src/regression/malloc-oom.exe [status 1] FAIL ./src/regression/putenv-doublefree-static.exe [signal Segmentation fault] FAIL ./src/regression/putenv-doublefree.exe [signal Segmentation fault] src/regression/setenv-oom.c:23: expected ENOMEM, got Operation not permitted FAIL ./src/regression/setenv-oom-static.exe [status 1] src/regression/setenv-oom.c:23: expected ENOMEM, got Operation not permitted FAIL ./src/regression/setenv-oom.exe [status 1] ****************************************************************************************************************************** Is the brk system call still kosher? I thought malloc was supposed to use something mmap. On Wed, Mar 30, 2016 at 12:47 PM, Szabolcs Nagy wrote: > * Max Ruttenberg [2016-03-30 12:18:33 > -0400]: > > I've built musl on an Ubuntu VM (x86_64 is the architecture) and have > > installed it to an install directory inside the downloaded clone. > > > > So the compiler is in: /path/to/musl/install/bin/musl-gcc > > > > The loader is in: /path/to/musl/install/lib/libc.so > > > > At the top level of libc-test I run a make like so: > > > > make CC=/path/to/musl/bin/musl-gcc RUN_WRAP=/path/to/musl/lib/libc.so > > > > that's not the intended usage > > RUN_WRAP is for qemu or similar tools for running the binaries > > you can specify the libc.so by changing the dynamic-linker name > (at least that's enough in case of musl) or installing the > musl-gcc wrapper/musl based toolchain with different dynamic-linker > name, e.g. > > make CC='/path/to/musl/bin/musl-gcc > -Wl,-dynamic-linker=/path/to/musl/lib/libc.so' > > should work (not tested) > > > The tests run, I don't get the "no such file or directory" error. But for > > some reason a bunch of tests fail that shouldn't according to the > Libc-Test > > wiki. What am I doing wrong? Are these tests dependent on system > resources > > that maybe I'm not providing e.g. enough memory? Do I need to run as a > sudo > > user as might be suggested by the "Operation not permitted" errors? > > > > static linked binaries cannot be loaded by libc.so so all *-static.exe > failed to run. > -Max --089e0117605b5715ac052f47632b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Szabolcs,

Thank you! That was helpful. = I have a couple of tests that still fail in functional but they clearly sta= te "64bit tests not implemented."
I still have a bunch = of tests that fail in regression though...

Running= a make like so:

make CC=3D'/path/to/musl/bin/musl-gcc -Wl,-dynamic-linker= =3D/path/to/musl/lib/libc.so'

this is what my src/regression/RE= PORT file looks like:

****************************= ***************************************************************************= ***********************
src/regression/malloc-brk-fail.c:33: malloc did no= t fail with ENOMEM, got Operation not permitted
FAIL ./s= rc/regression/malloc-brk-fail-static.exe [status 1]
src/regressio= n/malloc-brk-fail.c:33: malloc did not fail with ENOMEM, got Operation not = permitted
FAIL ./src/regression/malloc-brk-fail.exe [status 1]
src/regression/malloc-oom.c:16: expected ENOMEM, got Operation not = permitted
FAIL ./src/regression/malloc-oom-static.exe [status 1]<= /div>
src/regression/malloc-oom.c:16: expected ENOMEM, got Operation no= t permitted
FAIL ./src/regression/malloc-oom.exe [status 1]
=
FAIL ./src/regression/putenv-doublefree-static.exe [signal Segmentatio= n fault]
FAIL ./src/regression/putenv-doublefree.exe [signal Segm= entation fault]
src/regression/setenv-oom.c:23: expected ENOMEM, = got Operation not permitted
FAIL ./src/regression/setenv-oom-stat= ic.exe [status 1]
src/regression/setenv-oom.c:23: expected ENOMEM= , got Operation not permitted
FAIL ./src/regression/setenv-oom.ex= e [status 1]
*****************************************= ***************************************************************************= **********

Is the brk system call still kosher? I = thought malloc was supposed to use something mmap.=C2=A0

<= div class=3D"gmail_extra">
On Wed, Mar 30, 20= 16 at 12:47 PM, Szabolcs Nagy <nsz@port70.net> wrote:
* Max Ruttenberg <mruttenberg@emutechnology.com> [2016-03-30 12:18= :33 -0400]:
> I've built musl on an Ubuntu VM (x86_64 is the ar= chitecture) and have
> installed it to an install directory inside the downloaded clone.
>
> So the compiler is in: /path/to/musl/install/bin/musl-gcc
>
> The loader is in: /path/to/musl/install/lib/libc.so
>
> At the top level of libc-test I run a make like so:
>
> make CC=3D/path/to/musl/bin/musl-gcc RUN_WRAP=3D/path/to/musl/lib/libc= .so
>

that's not the intended usage

RUN_WRAP is for qemu or similar tools for running the binaries

you can specify the libc.so by changing the dynamic-linker name
(at least that's enough in case of musl) or installing the
musl-gcc wrapper/musl based toolchain with different dynamic-linker
name, e.g.

make CC=3D'/path/to/musl/bin/musl-gcc -Wl,-dynamic-linker=3D/path/to/mu= sl/lib/libc.so'

should work (not tested)

> The tests run, I don't get the "no such file or directory&quo= t; error. But for
> some reason a bunch of tests fail that shouldn't according to the = Libc-Test
> wiki. What am I doing wrong? Are these tests dependent on system resou= rces
> that maybe I'm not providing e.g. enough memory? Do I need to run = as a sudo
> user as might be suggested by the "Operation not permitted" = errors?
>

static linked binaries cannot be loaded by libc.so so all *-static.e= xe
failed to run.



-Max
--089e0117605b5715ac052f47632b--