From fnaumann@mail.cs.uni-magdeburg.de Fri Feb 13 21:32:19 2004 Date: Fri, 13 Feb 2004 21:25:01 +0100 To: mint@lists.fishpool.fi Subject: [MiNT] mintlib and shareable libraries From: Arnaud BERCEGEAY Content-Type: text/plain; format=flowed; charset=iso-8859-15 MIME-Version: 1.0 Message-ID: User-Agent: Opera7.23/Linux M2 build 518 Delivered-To: mint@lists.fishpool.fi X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: arnaud.bercegeay@free.fr Precedence: bulk List-help: List-unsubscribe: List-ID: X-List-ID: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by prinz.cs.uni-magdeburg.de id i1DKWHo03533 Hello, I have a question to make the thing clear in my mind: is mintlib ready to build "shareable" libraries (by shareable libraries i mean shareable slb or ldg) ? Here is just an example. A process (let's call it p1) call one of the library (slb/ldg) function. This function call malloc(), mintlib (within the ldg/slb) will perform a big Malloc(), and the area returned by malloc() will be a small part of the big Malloc. Who own this Malloc ? Is it the process that has called this library function (p1) ? Later, another process (p2) call the same library fuction, which one call once more malloc(). The area returned by this malloc will be another part of the Malloc() allocated in the previous call. At this moment, the 2nd process (p2) is working on a memory area owned by the 1st process. Right ? Later, if process 1 ended, mint will automatically free the memory allocated by this process, and so the big Malloc() of the library will be free-ed... and p2 will work on a memory that may be allocated by another process at any time. Am i right ? best regards, Arnaud.