From: "Luka Marčetić" <paxcoder@gmail.com>
To: musl@lists.openwall.com
Subject: Re: cluts review
Date: Wed, 13 Jul 2011 18:55:01 +0200 [thread overview]
Message-ID: <4E1DCDE5.1040008@gmail.com> (raw)
In-Reply-To: <20110713160327.GA24660@openwall.com>
On 07/13/2011 06:03 PM, Solar Designer wrote:
> Luka, Rich -
>
> The below is not criticism, but just some feedback on my test run of
> cluts earlier today.
>
> So, with the changes that I described before, I built cluts on a glibc
> 2.3.6'ish linux-threads system (yes, pre-NPTL).
> [...]
>
> As to cluts going to sleep, this is probably a bug in alloc.c. If this
> file is going to be rewritten, then it might not make sense to chase the
> bug down now. But it is useful to re-test the new version with low
> RLIMIT_AS as well.
Thanks for the tip.
> After a while, I killed the alloc thread that consumed the most CPU time.
>
> (BTW, all of them are just ./cluts in "ps" because cluts.c passes its
> own argv[0] to exec. Perhaps it'd be nicer to fix that.)
Wasn't aware of this. Will fix.
> The 'alloc' test collection crashed!
> Executing 'buf' test collection...
>
> I got lots of errors from "numeric" - I didn't bother recording most.
> The above are just a few of them.
In my opinion, the errors are warranted. But I asked Rich for review on
that one. In fact, the collection blocks a lot of error messages. Each
string that gets passed to multiple functions is printed only with the
first function that fails running with it (in your, strtoumax appears a
lot of times, because that's the first function that gets executed with
each string). The huge long long integer printout is I guess what makes
it look as if there are more messages than there are. Other than that,
it's probably the implementations. If it still turns out to be a test
data issue, let me know.
> The 'numeric' test collection failed 16384 test(s).
Hmm, is it an up-to-date version of cluts.c? The number is overblown.
> Executing 'string' test collection...
> The 'string' test collection passed.
String.c always does (it still returns 0 no matter what) ;-P
> Test collections passed: 1/4
>
> This is the known issue with number of failed test collections, right?
> Should have been 2, I guess.
This is the number of passed collections. I don't know why it says "out
of four" here, if you still have the buf.c-less version :-/
> Thanks,
>
> Alexander
Thank you for the review.
I'll offer my responses to feedback in form of commits :-)
Luka.
next prev parent reply other threads:[~2011-07-13 16:55 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-13 11:07 Solar Designer
2011-07-13 12:02 ` Luka Marčetić
2011-07-13 12:21 ` Solar Designer
2011-07-13 12:57 ` Luka Marčetić
2011-07-13 13:42 ` Rich Felker
2011-07-13 14:21 ` Solar Designer
2011-07-13 13:54 ` Solar Designer
2011-07-13 14:00 ` Rich Felker
2011-07-13 14:31 ` Solar Designer
2011-07-13 14:03 ` Rich Felker
2011-07-13 14:37 ` Solar Designer
2011-07-13 16:03 ` Solar Designer
2011-07-13 16:55 ` Luka Marčetić [this message]
2011-07-13 17:05 ` Solar Designer
2011-07-13 17:25 ` Luka Marčetić
2011-07-13 17:52 ` Solar Designer
2011-07-13 19:29 ` Luka Marčetić
2011-07-13 19:55 ` Rich Felker
2011-07-13 20:39 ` Solar Designer
2011-07-13 21:44 ` Solar Designer
2011-07-13 19:52 ` Rich Felker
2011-07-13 20:03 ` Rich Felker
2011-07-14 18:56 ` Rich Felker
2011-07-13 13:38 ` Rich Felker
2011-07-13 14:12 ` Solar Designer
2011-07-13 14:26 ` Rich Felker
2011-07-13 14:46 ` Solar Designer
2011-07-13 16:25 ` Luka Marčetić
2011-07-13 17:03 ` Solar Designer
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=4E1DCDE5.1040008@gmail.com \
--to=paxcoder@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).