public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
From: "Soni L." <fakedme+libc@gmail.com>
To: Libc-help <libc-help@sourceware.org>
Subject: The case for statically linked libc/pthread
Date: Sun, 27 Feb 2022 16:57:56 -0300	[thread overview]
Message-ID: <5e390a65-bcfc-5924-cd49-39222d640165@gmail.com> (raw)

It'd be nice if the kernel could keep track of which code segments
allocated memory or spawned threads, so that dlclose can release those
resources. In fact this is particularly important for correctness in
dlclose. But that requires libc to be statically linked in the first place.

There's no hope for dlclose without statically linked libc.

             reply	other threads:[~2022-02-27 19:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-27 19:57 Soni L. [this message]
2022-03-15 12:07 ` Adhemerval Zanella

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=5e390a65-bcfc-5924-cd49-39222d640165@gmail.com \
    --to=fakedme+libc@gmail.com \
    --cc=libc-help@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).