mailing list of musl libc
 help / color / mirror / code / Atom feed
From: aep <aep@exys.org>
To: <musl@lists.openwall.com>
Subject: Re: [PATCH] properly terminate linked link of dsos
Date: Wed, 12 Oct 2011 16:25:48 +0200	[thread overview]
Message-ID: <37ae4188867ea36022c6305ae687bd23@exys.org> (raw)
In-Reply-To: <20111012140141.GX132@brightrain.aerifal.cx>

On Wed, 12 Oct 2011 10:01:41 -0400, Rich Felker wrote:

> See line 357. This patch is a no-op.
>
> Rich


indeed. For the record (as dicussed on irc): calloc doesn't zero the 
memory for me.
Something entirely else is fishy.


  reply	other threads:[~2011-10-12 14:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-12 13:42 Arvid Ephraim Picciani
2011-10-12 14:01 ` Rich Felker
2011-10-12 14:25   ` aep [this message]
2011-10-12 14:46     ` aep
2011-10-14  1:03       ` Rich Felker
2011-10-14 21:11         ` Isaac Dunham
2011-10-14 22:53           ` 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=37ae4188867ea36022c6305ae687bd23@exys.org \
    --to=aep@exys.org \
    --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).