[gnutls-devel] eliminating gnutls_global_init

Daniel Kahn Gillmor dkg at fifthhorseman.net
Sat Nov 30 15:15:21 CET 2013

On 11/29/2013 07:01 PM, Nikos Mavrogiannopoulos wrote:
> The issues with having the initialization the constructor are
> * It is not clear what to do on initialization error (e.g. when some I/O
> fails)
> * There will be different semantics in static libraries (that call no
> constructors), which will still need to call gnutls_global_init and ELF
> shared libraries that will not.
> Any issues I've missed, or ideas?

how does this interact with tools that load gnutls via dlopen?  will
they need to do anything special, or will dlopen take care of it?  what
happens if a process dlopen()s the library twice? (e.g. via two separate
modules in the PAM stack or something horrible like that)


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 1027 bytes
Desc: OpenPGP digital signature
URL: </pipermail/attachments/20131130/685cb567/attachment.sig>

More information about the Gnutls-devel mailing list