mailing list of musl libc
 help / color / mirror / code / Atom feed
From: "Arvid E. Picciani" <aep@exys.org>
To: <musl@lists.openwall.com>
Subject: Re: ldso: dlclose.
Date: Thu, 23 Aug 2012 14:39:38 +0200	[thread overview]
Message-ID: <5603ddad712718518eed1430f5d00450@exys.org> (raw)
In-Reply-To: <20120820004803.GA27715@brightrain.aerifal.cx>

On Sun, 19 Aug 2012 20:48:03 -0400, Rich Felker wrote:

> To elaborate, removing a DSO from a process's address space is highly
> non-trivial and error-prone.

In fact it doesn't even work correctly in glibc.
It's just that usually no one notices.

When i see people using plugin architectures with unload,
it's almost always coming down from a  high level design.

The lack of any usable IPC in linux lead to glueing the
components into one process.
Plugins make it appear clean, but really it's not clean at all.
Much worse when C++ comes into the mix and arbitrary
things happen at the "abi" level.

Plugins are _not_ a good component separation design.
Neither are any of the alternatives, of course...

Another sad story of how the religious view of one kernel
maintainer creates a whole universe of bad design further down.



-- 
Arvid E. Picciani


  parent reply	other threads:[~2012-08-23 12:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-19 16:26 musl
2012-08-20  0:48 ` Rich Felker
2012-08-22 22:41   ` Rich Felker
2012-08-23 12:39   ` Arvid E. Picciani [this message]
2012-08-23 12:48     ` Rich Felker
2012-08-23 16:02       ` orc
2012-08-23 18:01         ` Rich Felker
2012-08-24  7:52           ` musl
2012-08-24 12:27             ` Rich Felker
2012-08-24 13:54               ` musl
2012-08-24 17:46                 ` Rich Felker
2012-08-25  7:54                   ` boris brezillon

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=5603ddad712718518eed1430f5d00450@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).