From: "Luka M." <paxcoder@gmail.com>
To: musl@lists.openwall.com
Subject: Re: Daily cluts reports - malloc rewrite
Date: Thu, 21 Jul 2011 03:30:24 +0200 [thread overview]
Message-ID: <CAHf7i5SJmjDLs8+B9GbBtnjx367ySvvPPqF1WbvqAyu_MZH_OQ@mail.gmail.com> (raw)
Hey guys.
I spent the whole day yesterday trying to get some kind of *nix
running here. Now I'm using aptosid on a VM. Anyway, today I've
rewritten malloc.c (modularity yay), but I haven't yet managed to
debug it. That means if you look at the file, you'll get the gist of
it, but the test collection doesn't behave correctly yet, so that's
something for e to do tomorrow.
Hope you're fine. It's uberlate here, so I'm going to crash right away.
That's it for now :-)
Luka.zzZZZ
reply other threads:[~2011-07-21 1:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAHf7i5SJmjDLs8+B9GbBtnjx367ySvvPPqF1WbvqAyu_MZH_OQ@mail.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).