Re: Report nptl 0.56

Martin Schlemmer <[email protected]>
Newsgroups gmane.comp.lib.phil
Message-ID <[email protected]>
Hi

> i686-pc-linux-gnu
> linux-2.6.0-test2
>
> Tools used:-
>
> FSF gcc-3.3.1-cvs
> HJL binutils-2.14.90.0.5
>

Fairly the same setup, just with some Redhat patches to binutils,
and current gcc-3_3-rhl-branch.

Kernels tested was 2.6.0-test2, 2.6.0-test2-bk[345] and NPTL-0.5[56]
with glibc snapshots from the third if I remember correctly.

> The testsuite fails a few tests for me:-
>
> make[2]: *** [/mnt/hdb6/home/gws/scratch/tempo/glibc-build/nptl/tst-kill1.out] Error 1
> make[2]: *** [/mnt/hdb6/home/gws/scratch/tempo/glibc-build/nptl/tst-join1.out] Error 1
> make[2]: *** [/mnt/hdb6/home/gws/scratch/tempo/glibc-build/nptl/tst-fork3.out] Terminated
> make[2]: *** Deleting file `/mnt/hdb6/home/gws/scratch/tempo/glibc-build/nptl/tst-fork3.out'
> make[2]: *** [/mnt/hdb6/home/gws/scratch/tempo/glibc-build/nptl/tst-exec3.out] Error 1
> make[2]: *** [/mnt/hdb6/home/gws/scratch/tempo/glibc-build/nptl/tst-exec4.out] Error 1
> make[2]: *** [/mnt/hdb6/home/gws/scratch/tempo/glibc-build/nptl/tst-exit1.out] Error 1
> 
> tst-fork3 sometimes works, sometimes doesn't. On this occasion I manually
> killed it to keep the testsuite running.
>

Fairly the same here.  Here tst-kill1 and tst-join1 usually exit with:

  Failed to killed test process: No child processes

Snapshots of glibc on 20030723 still worked fine (NPTL-0.55).

> The 2.6.0-test2 kernel also throws up a couple of oops's during the
> testsuite run which I've reported separately to the kernel folk. Maybe the
> kernel is responsible for the above failures. Dunno.

No oopses here.


Thanks,

-- 

Martin Schlemmer
signature.asc (application/pgp-signature, 189 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQA/MVB9qburzKaJYLYRAmeTAJ9ek0RNP0Amy3SWUK/Qoql6K+BY4wCcDr5K
Y/YLxq1UnxiDdc0+eo+ZhMg=
=Tr54
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.