[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [MiNT] mktbl.c - not a single free() but several malloc's
- To: ole@monochrom.net
- Subject: Re: [MiNT] mktbl.c - not a single free() but several malloc's
- From: Miro Kropacek <miro.kropacek@gmail.com>
- Date: Tue, 10 Aug 2010 21:24:33 +0200
- Cc: mint@lists.fishpool.fi
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=Ys06xuxkkPC8SmWm+ygbrrB7sGn1jr2X26Q2xeJ5J6A=; b=rm7KRoQ7yz0Ne8haWO49/NszzcdKdLE18dMIu9Z4anf5iXuBK3ZorEXUzbXRPrXkwa 4/k2LDrSTV+BEmcqn3YrgydXnVMSf6WWuBiJ1e0080fG7+wsUNSFDB1P7s1wEC96LbhW rt+ZGS/GNjevNjI+UJH9rlZj+kTVpLVP9AzDM=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=XnCVac9VAgeC+mNjq4P736qZ3Jo8N3sXX+Mbcd1opmUGokhO5Ajk4uiBg++PN2TpYc LGkSm7HjC+25bj8BCknfDLzMinzetjW8V11MJ0AS7Bs8mqwwLbZ2BfvHlen8vGC2libU 1wWfJQiBsyA6r6vPmhwKZTh8jEJh3TesmXRlE=
- In-reply-to: <ca8d510e91c4b5ed58f03bd71f012c65-EhVcX1lFRQVaRwYcDTpQCEFddQZLVF5dQUNBAjBTXF5bVkYJXlZoBl06XF1XQEEEWFJZRA==-webmailer1@server08.webmailer.hosteurope.de>
- List-help: <mailto:ecartis@lists.fishpool.fi?Subject=help>
- List-id: <mint.lists.fishpool.fi>
- List-owner: <mailto:tjhukkan@fishpool.fi>
- List-post: <mailto:mint@lists.fishpool.fi>
- List-subscribe: <mailto:mint-request@lists.fishpool.fi?Subject=subscribe>
- List-unsubscribe: <mailto:mint-request@lists.fishpool.fi?Subject=unsubscribe>
- References: <ca8d510e91c4b5ed58f03bd71f012c65-EhVcX1lFRQVaRwYcDTpQCEFddQZLVF5dQUNBAjBTXF5bVkYJXlZoBl06XF1XQEEEWFJZRA==-webmailer1@server08.webmailer.hosteurope.de>
- Sender: mint-bounce@lists.fishpool.fi
> I just had a quick look at mktbl.c - and the first thing that I recognize
> is that it doesn't free the memory that was allocated with malloc();
>
> Is that OK, will freemint free that memory? What If I run that tool with
> plain TOS?
All memory is free'ed as soon as you terminate a process (except TSRs,
logically). So it isn't that bad, don't worry :) But it's nice
programming habit to release everything before exit, sure.
--
MiKRO / Mystic Bytes
http://mikro.atari.org