From: DJ Delorie <dj@redhat.com>
To: Siddhesh Poyarekar <siddhesh@sourceware.org>
Cc: adhemerval.zanella@linaro.org, libc-alpha@sourceware.org,
carlos@redhat.com
Subject: Re: sbrk() failure while processing tunables
Date: Tue, 02 Nov 2021 23:15:14 -0400 [thread overview]
Message-ID: <xn5yta7wvx.fsf@greed.delorie.com> (raw)
In-Reply-To: <ef688a14-9d35-6b4a-f3be-52570792f2ff@sourceware.org>
Siddhesh Poyarekar <siddhesh@sourceware.org> writes:
> That'll work only for the dynamic case, you'll need special code for
> static linking then. Alternatively, the rtld_malloc code looks
> sufficiently independent that it could be split out into its own file
> and included directly into dl-tunables.c.
That implies that statically linked executables would have two
independent malloc implementations...
next prev parent reply other threads:[~2021-11-03 3:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 16:54 Adhemerval Zanella
2021-11-01 17:17 ` Siddhesh Poyarekar
2021-11-02 19:56 ` Adhemerval Zanella
2021-11-03 3:12 ` Siddhesh Poyarekar
2021-11-03 3:15 ` DJ Delorie [this message]
2021-11-03 3:25 ` Siddhesh Poyarekar
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=xn5yta7wvx.fsf@greed.delorie.com \
--to=dj@redhat.com \
--cc=adhemerval.zanella@linaro.org \
--cc=carlos@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=siddhesh@sourceware.org \
/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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).