mailing list of musl libc
 help / color / mirror / code / Atom feed
From: u-igbb@aetey.se
To: Rich Felker <dalias@aerifal.cx>
Cc: musl@lists.openwall.com
Subject: Re: malloc not behaving well when brk space is limited?
Date: Sat, 29 Mar 2014 19:54:22 +0000	[thread overview]
Message-ID: <20140329195422.GM8221@example.net> (raw)
In-Reply-To: <20140329185619.GX26358@brightrain.aerifal.cx>

On Sat, Mar 29, 2014 at 02:56:19PM -0400, Rich Felker wrote:
> Yes, I understand. I didn't mean that this can't or shouldn't be
> fixed, just that the changes I had hoped to make to malloc in the
> 1.1.x series are not looking like the right direction for fixing this,
> so we're back to the question of what to do.
> 
> If you need a fix (or at least a workaround) right away, let me know
> and I'll see if I can think of anything.

Thanks Rich,

I would appreciate your support for any tenable solution.

The very ugly workaround which I am testing now is to temporarily
resort to the implicit loader. This seems to work, with a hack of the
kind I posted at first, introducing a "ONCE_LD_LIBRARY_PATH" variable
and renaming it afterwards (introducing the possible slight environment
corruption).

This is far from a solution, just slightly better than a complete halt.

Nevertheless I feel moving to musl if worth the effort.

So if you can think of any half-usable solution to make malloc compatible
with the standalone loader, I would happily go for it.

Regards,
Rune



  reply	other threads:[~2014-03-29 19:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-29 17:00 u-igbb
2014-03-29 17:15 ` Timo Teras
2014-03-29 17:22   ` Rich Felker
2014-03-29 18:02     ` u-igbb
2014-03-29 18:56       ` Rich Felker
2014-03-29 19:54         ` u-igbb [this message]
2014-03-29 20:25           ` Rich Felker
2014-03-29 20:54             ` u-igbb
2014-03-31  4:51               ` 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=20140329195422.GM8221@example.net \
    --to=u-igbb@aetey.se \
    --cc=dalias@aerifal.cx \
    --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).