On Sat, Jun 12, 2004 at 02:57:18PM -0700, Nicholas Clark wrote:
> I suspect a memory corruption bug, as it it doesn't look like the specific
> arguments to this malloc are bogus. I can't recreate this problem at all
> on x86 FreeBSD or on OS X. I find the x86 FreeBSD non-recreatability
> surprising.
Er, oops. OS X wasn't uptodate. Test 8 crashes. Will the guard malloc I get
further:
(gdb) print data[512]
Cannot access memory at address 0xb30a3000
(gdb) where
#0 0x001b6004 in Parrot_FixedFloatArray_set_number_keyed_int (interpreter=0xb000ec6c,
pmc=0xb0654748, key=513, value=17.300000000000001) at classes/fixedfloatarray.c:233
#1 0x001b6118 in Parrot_FixedFloatArray_set_string_keyed_int (interpreter=0xb000ec6c,
pmc=0xb0654748, key=513, value=0xb003fc88) at classes/fixedfloatarray.c:257
The crash is the last line of:
new P0, .FixedFloatArray
set P0, 1024
set P0[25], 125
set P0[128], 10.2
set P0[513], "17.3"
Nicholas Clark
