Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sun, 07 Aug 2011 04:41:33 +0200
From: Luka Marčetić <>
Subject: Re: New daily reports - debugging alloc.c still

What the title says.

* figure out how to continue writing pthread_eintr.c so that it works 
regarless of the nr of cores, write as many of function tests as possible
* apply different tools on setuid.c to remove the hang, employ the 
strategy from point one here as well
(in both cases, the program is trying to interrupt a child's function call)
* go through alloc.c again, to hopefully get an idea of why there are 
"unexpected features".

P.S. Attached is my to-report | grep -v musl #because i've recompiled musl

View attachment "to-report-grep" of type "text/plain" (626 bytes)

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.