gnupic: Re: [gnupic] gpasm memory leaks
Subject:
Re: [gnupic] gpasm memory leaks
From:
Ian Jackson ####@####.####
Date:
4 Jun 2007 17:02:31 +0100
Message-Id: <18020.14229.45378.977752@chiark.greenend.org.uk>
David Barnett writes ("Re: [gnupic] gpasm memory leaks"):
> A status update on the memory leaks for those interested: [...]
Sorry to rain on your parade, but I have to ask: _why_ are we fixing
memory leaks in a PIC assembler ? Even if the assembler is hugely
profligate with memory allocation the amount of RAM used during an
assembly is bounded to a few times the size of the flash in the
device or a few times the size of the input file (larger of those,
obviously).
The obvious conclusion is that the gpasm code shouldn't ever call
`free'. That way there can be no double-free bugs or use-after-free
bugs and the like.
Ian.
