At 02:39 AM 9/13/2001 -0700, Josh Wilmes wrote:
>Yeah at this point I figure the allocation stuff isn't that useful.
>However the "uninitialized memory read", "invalid pointer read", and
>"free memory write" errors might be of interest.
Those were the ones I was worried about. They show we're do
Yeah at this point I figure the allocation stuff isn't that useful.
However the "uninitialized memory read", "invalid pointer read", and
"free memory write" errors might be of interest.
--Josh
At 10:18 on 09/13/2001 BST, Simon Cozens <[EMAIL PROTECTED]> wrote:
> On Thu, Sep 13, 2001 at 02:2
On Thu, Sep 13, 2001 at 02:21:16AM -0700, Josh Wilmes wrote:
> There are a few interesting things in here which look like they may be
> real errors. (i'd ignore the PLKs for now)
Thanks for doing this, but to be honest, I expect our memory allocation
to be all to hell because we have no freeing
FYI..
There are a few interesting things in here which look like they may be
real errors. (i'd ignore the PLKs for now)
--Josh
perl assemble.pl t/test.pasm > t/test.pbc
./test_prog t/test.pbc > t/test.out
Purify instrumented test_prog (pid 17982 at Thu Sep 13 02:08:41 2001)
* Purify
