From: "Luka Marčetić" <paxcoder@gmail.com>
To: musl@lists.openwall.com
Subject: Re: New daily reports - debugging alloc.c et al
Date: Sat, 06 Aug 2011 06:40:12 +0200 [thread overview]
Message-ID: <4E3CC5AC.3070404@gmail.com> (raw)
In-Reply-To: <4E3B331E.7050502@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1360 bytes --]
On 08/05/2011 02:02 AM, Luka Marčetić wrote:
> I tried to do the above, but got pretty stuck, so I'll have to finish
> it tomorrow unfortunately.
> Accordingly, priorities are:
> *finish pthread_eintr.c
> *decide about the generator, take another task
> Attached is the diff form of the above report.
>
> Talk to you soon.
> Luka.
Hello
The day started with Szabolcs suggesting I use valgrind to debug
alloc.c. A very good idea, one which changed my priorities. Rich
explained to me how memory management works behind the scenes (an
explanation I very much needed), and suggested an mmap-based method to
employ to find bugs. I've been changing the prog until now (6am here),
but the method of allocation that I've been recommended either fails to
fulfill its promise, or I'm blind to my own bug.
Here's a minimal test case:
http://paste.debian.net/125242/
A quick explanation: Alloc.c needs to squat most of process' virtual
memory. I employ a kind of binary search to find the greatest size that
can be allocated, but then it turns out, mmap and malloc are able to
continue allocating memory still. Not sure why.
Priorities:
* finish this test collection for good (need your replies for that)
* work on pthread_eintr.c
That's it for today.
Luka
P.S. Lost diff history, attached is repo vs local /tests diff, come
commits not included
[-- Attachment #2: to-report --]
[-- Type: text/plain, Size: 529 bytes --]
a.out |binary
alloc |binary
alloc.c | 177 ++++++++++++++--------
alloc.c.older | 358 +++++++++++++++++++++++++++++++++++++++++++++
alloc.c~ | 406 ++++++++++++++++++++++++++++++++++++++++++++++++++++
common/common.h | 1
common/common.h.gch |binary
common/e_name.c~ | 32 ++++
common/testgen.c | 66 ++++++++
common/testgen.c~ | 66 ++++++++
pthread_eintr.c | 129 ++++++++++++++++
11 files changed, 1170 insertions(+), 65 deletions(-)
next prev parent reply other threads:[~2011-08-06 4:40 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-03 22:14 New daily reports Luka Marčetić
2011-08-03 22:46 ` Solar Designer
2011-08-04 10:51 ` Luka Marčetić
2011-08-04 11:54 ` Solar Designer
2011-08-04 12:01 ` Luka Marčetić
2011-08-04 12:12 ` Solar Designer
2011-08-05 0:02 ` New daily reports - started pthread_eintr.c Luka Marčetić
2011-08-05 0:10 ` Solar Designer
2011-08-06 4:40 ` Luka Marčetić [this message]
2011-08-06 11:15 ` New daily reports - debugging alloc.c et al Szabolcs Nagy
2011-08-06 11:50 ` Szabolcs Nagy
2011-08-06 14:34 ` Szabolcs Nagy
2011-08-06 15:38 ` Szabolcs Nagy
2011-08-07 2:41 ` New daily reports - debugging alloc.c still Luka Marčetić
2011-08-07 2:50 ` Solar Designer
2011-08-07 7:32 ` Rich Felker
2011-08-07 22:25 ` Luka Marčetić
2011-08-09 3:02 ` New daily reports - buf.c Luka Marčetić
2011-08-10 1:34 ` New daily reports - nothing Luka Marčetić
2011-08-10 1:38 ` Rich Felker
2011-08-10 11:47 ` Luka Marčetić
2011-08-10 2:02 ` Solar Designer
2011-08-10 11:23 ` Luka Marčetić
2011-08-10 11:56 ` Solar Designer
2011-08-10 12:13 ` Luka Marčetić
2011-08-10 2:07 ` Solar Designer
2011-08-10 2:12 ` Rich Felker
2011-08-10 4:59 ` Rich Felker
2011-08-10 12:09 ` Luka Marčetić
2011-08-10 12:44 ` Luka Marčetić
2011-08-10 14:25 ` Rich Felker
2011-08-10 17:21 ` Luka Marčetić
2011-08-10 17:33 ` Rich Felker
2011-08-10 18:23 ` Luka Marčetić
2011-08-10 18:21 ` Rich Felker
2011-08-10 18:34 ` Luka Marčetić
2011-08-10 18:33 ` Rich Felker
2011-08-14 20:00 ` Rich Felker
2011-08-15 14:14 ` Luka Marčetić
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=4E3CC5AC.3070404@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).