From: Timerlan Moldobaev <moldobaev@gmail.com>
To: musl@lists.openwall.com
Subject: Re: cluts test suite with musl
Date: Wed, 24 Apr 2013 15:26:57 +0300 [thread overview]
Message-ID: <CAE+eE2KGbtpXFO8_+Vu9XSea4R+XrcF-Q79DeTnXBPiPw9RAyg@mail.gmail.com> (raw)
In-Reply-To: <20130423154705.GB20323@brightrain.aerifal.cx>
[-- Attachment #1: Type: text/plain, Size: 2256 bytes --]
Thanks !
I applied the patch. Still have some tests failing.
For instance tests/buf fails with the following error message:
iconv(&<"abcd">, &<4>, &s, &<3>) caused a SIGSEGV!
I am not sure but it seems that iconv() that is called from wrap_iconv()
should return an error return value and set an errno value.
At least to my understanding that the way the test is written.
For musl implementation of iconv() returns 0 and sets no errno.
While in the case of standard Linux implementation, errno = E2BIG and -1
returned ( error return value) .
For the case buf linked dynamically against the standard libc.so library:
ldd tests/buf
libpthread.so.0 => /lib64/libpthread.so.0 (0x00000030d1000000)
librt.so.1 => /lib64/librt.so.1 (0x00000030d4400000)
libm.so.6 => /lib64/libm.so.6 (0x00000030d0800000)
libc.so.6 => /lib64/libc.so.6 (0x00000030d0400000)
/lib64/ld-linux-x86-64.so.2 (0x00000030cf400000)
> uname -a
Linux lnxbdc96 2.6.18-164.11.1.el5 #1 SMP Wed Jan 6 13:26:04 EST 2010
x86_64 x86_64 x86_64 GNU/Linux
Can you please look into this ?
Thanks.
On Tue, Apr 23, 2013 at 6:47 PM, Rich Felker <dalias@aerifal.cx> wrote:
> On Tue, Apr 23, 2013 at 11:31:27AM -0400, Rich Felker wrote:
> > On Tue, Apr 23, 2013 at 06:17:15PM +0300, Timerlan Moldobaev wrote:
> > > Can you please specify what tests within cluts should work
> correctly ?
> > > There are chances that in my specific environment some musl issues
> might
> > > pop up even when running cluts partly.
> > > I can assist in debugging such issues (as it was for testsuite case).
> >
> > Yes, I'm actually working on a patch right now that disables the
> > incorrect tests and fixes up some other issues.
>
> Here's the patch. I've just disabled the EINTR test module entirely
> since it's full of wrong code including broken attempts at
> synchronization based on a volatile variable, and attempts to unlock a
> lock that's already unlocked.
>
> The other main issue was invalid numeric tests.
>
> Note that the setuid race test will not work without root, and I don't
> think it's reliable anyway. There's an alternate test for this issue
> on the glibc bug tracker:
>
> http://sourceware.org/bugzilla/show_bug.cgi?id=13347
>
> Rich
>
[-- Attachment #2: Type: text/html, Size: 3356 bytes --]
next prev parent reply other threads:[~2013-04-24 12:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-23 12:26 Timerlan Moldobaev
2013-04-23 13:40 ` Rich Felker
2013-04-23 15:17 ` Timerlan Moldobaev
2013-04-23 15:31 ` Rich Felker
2013-04-23 15:47 ` Rich Felker
2013-04-24 12:26 ` Timerlan Moldobaev [this message]
2013-04-24 13:32 ` Rich Felker
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=CAE+eE2KGbtpXFO8_+Vu9XSea4R+XrcF-Q79DeTnXBPiPw9RAyg@mail.gmail.com \
--to=moldobaev@gmail.com \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).