pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: David Terrell <dbt@meat.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@postgresql.org
Subject: Re: RTLD_LAZY considered harmful (Re: pltlc and pltlcu
Date: Thu, 14 Feb 2002 18:08:42 -0800
Message-ID: <20020214180842.B23916@pianosa.catch22.org> (raw)
In-Reply-To: <18523.1013474997@sss.pgh.pa.us>
References: <Pine.LNX.4.30.0201211148030.687-100000@peter.localdomain>
	<25459.1013389242@sss.pgh.pa.us>
	<18523.1013474997@sss.pgh.pa.us>

On Mon, Feb 11, 2002 at 07:49:57PM -0500, Tom Lane wrote:
> I also believe that this will produce more consistent cross-platform
> behavior: so far as I could learn from googling, systems that do not
> define RTLD_NOW/RTLD_LAZY all act as though the mode were RTLD_NOW,
> ie, immediate binding.
> 
> Any objections to modifying all the port/dynloader files this way?

OpenBSD:
     The dlopen() function takes a name of a shared object as its first argu-
     ment.  The shared object is mapped into the address space, relocated, and
     its external references are resolved in the same way as is done with the
     implicitly loaded shared libraries at program startup.

     The path argument can either be an absolute pathname or it can be of the
     form ``lib<name>.so[.xx[.yy]]'' in which case the same library search
     rules apply that are used for ``intrinsic'' shared library searches.  The
     second argument currently has no effect, but should be set to DL_LAZY for
     future compatibility.

That last sentence being key....

-- 
David Terrell             | "War is peace, 
Prime Minister, Nebcorp   | freedom is slavery, 
dbt@meat.net              | ignorance is strength 
http://wwn.nebcorp.com/   | Dishes are clean." - Chris Fester



view thread (17+ messages)

Message-ID: <20020214180842.B23916@pianosa.catch22.org>
Permalink:  ../20020214180842.B23916@pianosa.catch22.org/
Also on:    postgresql.org/message-id/20020214180842.B23916@pianosa.catch22.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: dbt@meat.net, tgl@sss.pgh.pa.us, pgsql-hackers@postgresql.org
  Subject: Re: RTLD_LAZY considered harmful (Re: pltlc and pltlcu
  In-Reply-To: <20020214180842.B23916@pianosa.catch22.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox