On Thursday 14 June 2007 22:17:25 Mark Glines wrote:
> I poked around a bit in gdb. I don't have any answers or patches, but
> hopefully a little more information will be helpful.
>
> In Parrot_get_HLL_id, between the 31st and 32nd calls to this function,
> the string memory for the "name" string, from the "name_pmc" PMC, is
> freed. The string pointer is not updated. So, the next time around,
> segfault.
That's consistent with what I saw, too.
> Valgrind has some very interesting things to say about this test
> script, including lots of undefined data warnings, lots of accesses
> outside of allocated ranges, and also such gems as "definitely lost:
> 1,476,179 bytes in 13,925 blocks".
Here's my Valgrind alias:
alias vgp='valgrind --suppressions=~/dev/parrot/tools/dev/parrot.supp \
--num-callers=500 --leak-check=full --leak-resolution=high \
--show-reachable=yes parrot --leak-test'
That ought to help.
-- c
