[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bug-libsigsegv] libsigsegv under LGPL ?

From: Daniel Diaz
Subject: Re: [bug-libsigsegv] libsigsegv under LGPL ?
Date: Mon, 18 Jun 2012 19:03:18 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1

Hi Bruno,

thank you for your answer.

Bruno Haible wrote:
> LGPL means that proprietary programs can use the code just by linking
> to our library. The libsigsegv is a significant functionality; it can
> enable globally visible features like robustness or a decent garbage
> collector. Can you mention reasons why it would be good for the GNU
> project to allow these features to be used, at zero cost, by
> proprietary programs?

All GNU libraries provide significant functionalities ;-) Some are under GPL (readline), some under LGPL (GMP), some under another license (ncurses),... I don't try to understand/justify these choices :-). A library released under LGPL is easier to integrate in gprolog (specially for the core engine of gprolog). Thus my question about LGPL.

>> Other question: is your library thread-safe ?
> The library has global variables and global state. Therefore you need
> to ask more specifically: What are the operations that you wish to
> perform in different threads, without explicit locking on your side?

Suppose 2 threads sharing a buffer (a stack actually) on which a local handler has been installed with libsigsegv. Both access the buffer using locks. When an overflow occurs, is the libsigsegv code thread- safe (the code catching the signal and calling the user handler) ?


Ce message a ete verifie par MailScanner
pour des virus ou des polluriels et rien de
suspect n'a ete trouve.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]