From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/418 Path: news.gmane.org!not-for-mail From: =?UTF-8?B?THVrYSBNYXLEjWV0acSH?= Newsgroups: gmane.linux.lib.musl.general Subject: Re: New daily reports - nothing Date: Mon, 15 Aug 2011 16:14:12 +0200 Message-ID: <4E4929B4.1090401@gmail.com> References: <20110803224651.GB11437@openwall.com> <4E3A79B2.8090204@gmail.com> <4E3B331E.7050502@gmail.com> <4E3CC5AC.3070404@gmail.com> <4E3DFB5D.8040008@gmail.com> <20110807073224.GG132@brightrain.aerifal.cx> <4E3F10C7.4060601@gmail.com> <4E40A33F.7090804@gmail.com> <4E41E020.7020109@gmail.com> <20110810045933.GW132@brightrain.aerifal.cx> <20110814200044.GM132@brightrain.aerifal.cx> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: dough.gmane.org 1313417811 1735 80.91.229.12 (15 Aug 2011 14:16:51 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Mon, 15 Aug 2011 14:16:51 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-419-gllmg-musl=m.gmane.org@lists.openwall.com Mon Aug 15 16:16:47 2011 Return-path: Envelope-to: gllmg-musl@lo.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by lo.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1QsxyA-00025K-Jq for gllmg-musl@lo.gmane.org; Mon, 15 Aug 2011 16:16:46 +0200 Original-Received: (qmail 23962 invoked by uid 550); 15 Aug 2011 14:16:45 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 23952 invoked from network); 15 Aug 2011 14:16:45 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=H3qtbT1b0DLWUN2IZ6WdTqF1EvdLh6qNGPQ7alemLmI=; b=W89SNtHbVk+2efTjnuoOZX9fQ+CXH6juqCkKpLMd9Yxq83VGcYhlo3OTnY5pvrz2yD pWqG6c6CjXn7ENGS87A+yoEFMy3lxs72eahd/o344OGny0pnCzLL2H24xGvQWXYuB5IB 6ZQLQQRIqvTYf3uWjSrhbLn3/2lKDAWToaQSg= User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.18) Gecko/20110626 Icedove/3.1.11 In-Reply-To: <20110814200044.GM132@brightrain.aerifal.cx> Xref: news.gmane.org gmane.linux.lib.musl.general:418 Archived-At: On 08/14/2011 10:00 PM, Rich Felker wrote: > On Wed, Aug 10, 2011 at 12:59:33AM -0400, Rich Felker wrote: >> As I see it, what you've got (in varying stages of completeness) is >> categories 1, 2, 3, 6, 8, and 9, from the project description here: >> >> http://openwall.info/wiki/musl/unit-tests >> >> Here are the things I would like you to focus on right now, roughly in >> order of priority: >> [...] >> 1. Fixing issues with test validity, like the buffer overflow/heap >> [...] >> 2. Documenting the tests you have: what assertions they test. As >> [...] >> 3. Cleaning up the build system and source to make sure it builds >> [...] >> 4. Finish testing additional areas in the categories you're already >> [...] >> 5. Test categories 4 and 5. I think it would be nice to pull in some > Luka, could you please reply with an estimate on how many hours of > work you think each of these areas will take you and an intended > schedule for how and when you plan to accomplish them? > > Rich Hello. Work required for the above: 1. Depends on what the issues really are. Eg. valgrind is clean on alloc.c, but it still fails for musl on 64-bit, because I get nothing allocated following vm_limit. Explicitly putting malloc() after it works, but doing it via the function fails. It's really hard to debug child processes (which is how a lot of collections are written), I should perhaps try Alexander's method. But I really can't say how much it'll take me - depends on inspiration and help i get from others. It's been time consuming up until now, but I think I've polished it enough so I just need to spot this one thing I'm missing and then correction won't be a problem. 2. I've updated pthread_eintr.c. If there's something you want me to expound on, let me know. I can try and generate doxygen docs now. Not sure if we need more user documentation, but I could add a few more sentences to README just so that people know what to expect when they run ./cluts etc. (a few hours to setup, and update docs if there are errors) 3. I can make buf.c collection test whether MUSL is defined just as I've recently have done for pthread_eintr.c. I'd appreciate if someone could tell me how to add `install-musl` which should add an additional -DMUSL=1 flag. (this and testing it shouldn't take more than a couple hours). 4. and 5. Check IRC please about pthread_eintr.c. Also, I'd like to finish string.c before starting new collections if that's fine with me. Based on past experience, I believe that rewriting string.c will take me about three days of intensive work. I can't give you my estimate for tests 4 and 5 (sprintf and stdio tests), because other than the "example" given in 4, I don't know what else will need to be tested, and I don't know how exactly autoconf looks like. Schedule for the above: I can do 2 and 3 today, then start working on (either part of nr 5 or) string.c, and after that, come back to 1. Now I can't commit after Saturday, but I can still do nr 4, and after that 5 when I have time (college starts, so maybe not right away). When I'm done with 2 and 3 today, I can take a look at autoconf, and perhaps give you an estimate for that. If you have other suggestions, please let me know soon. Luka