From mint-bounce@lists.fishpool.fi Tue Jan 26 21:04:43 2010 Message-ID: <4B5F9E76.7070205@freesbee.fr> Date: Wed, 27 Jan 2010 03:01:26 +0100 From: =?ISO-8859-1?Q?Vincent_Rivi=E8re?= User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1 MIME-Version: 1.0 To: mint@lists.fishpool.fi Subject: Re: [MiNT] Freeing child's base page References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed X-Antivirus: avast! (VPS 100126-1, 26/01/2010), Outbound message X-Antivirus-Status: Clean X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: vincent.riviere@freesbee.fr Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.sparemint.org id o0R24hjk029917 Miro Kropacek wrote: > Now, easy answer would be "freeing child's basepage invalidates also its > data" but I doubt this makes any sense. Humm... For me it's normal. If I'm not wrong, for one process there are 2 Malloc() blocks: - The process environment block - The TPA block: basepage+text+data+bss+stack So if you call Mfree() with the pointer to the basepage, you actually free the whole TPA block, so the data becomes invalid. Am I wrong ? -- Vincent Rivière