From: JIghtuse <jightuse@gmail.com>
To: "Musl!" <musl@lists.openwall.com>
Subject: malloc testing
Date: Wed, 27 Apr 2011 10:24:15 +0700 [thread overview]
Message-ID: <4DB78C5F.8030803@gmail.com> (raw)
So, I am still working on testing malloc() of musl. My coding breaks by
some increase of studing in university, but I have to say I want to
participate. Is it real to join Summer of Security? After finished musl
tests I want to try blists development also.
--
Sincerely yours, JIghtuse.
next reply other threads:[~2011-04-27 3:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-27 3:24 JIghtuse [this message]
2011-04-29 5:42 ` Solar Designer
2011-06-04 18:03 ` JIghtuse
-- strict thread matches above, loose matches on Subject: below --
2011-04-10 15:59 malloc testing (was: Simple testing task - string functions) JIghtuse
2011-04-20 4:34 ` malloc testing (was: Simple testing task - string Rich Felker
2011-04-21 2:11 ` malloc testing JIghtuse
2011-04-21 6:00 ` Rich Felker
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=4DB78C5F.8030803@gmail.com \
--to=jightuse@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).