In message <[EMAIL PROTECTED]>
Steve Fink <[EMAIL PROTECTED]> wrote:
> +Stability
> +---------
> + Purify and other memory badness detectors
One thing that may be useful here is valgrind, which can be found
at http://developer.kde.org/~sewardj/ and does Purify types things
on linux.
I just hacked the parrot test suite to run parrot under valgrind
and it has only come up with one problem in t/op/hacks1, the details
of which are as follows:
valgrind-20020329, a memory error detector for x86 GNU/Linux.
Copyright (C) 2000-2002, and GNU GPL'd, by Julian Seward.
For more details, rerun with: -v
Syscall param open(pathname) contains uninitialised or unaddressable byte(s)
at 0x403F1892: __libc_open (__libc_open:31)
by 0x403829C3: _IO_fopen@@GLIBC_2.1 (iofopen.c:67)
by 0x809B287: cg_core (core.ops:138)
by 0x80955E0: runops_fast_core (runops_cores.c:34)
Address 0x4104051D is 3201 bytes inside a block of size 32824 alloc'd
at 0x4003DCC2: malloc (vg_clientmalloc.c:618)
by 0x8092E11: mem_sys_allocate (memory.c:74)
by 0x8098DAD: Parrot_alloc_new_block (resources.c:830)
by 0x8092EC0: mem_setup_allocator (memory.c:108)
ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
malloc/free: in use at exit: 249652 bytes in 54 blocks.
malloc/free: 58 allocs, 4 frees, 381692 bytes allocated.
For a detailed leak analysis, rerun with: --leak-check=yes
For counts of detected errors, rerun with: -v
I haven't attempted to look at this and see what is causing it.
Tom
--
Tom Hughes ([EMAIL PROTECTED])
http://www.compton.nu/
