Michael Scott <[EMAIL PROTECTED]> wrote:
t/src/hash.t
test 7 fails on Mac OS X 10.2.6 (gcc 3.3) because BIGLEN is too big: 99999.
100_000 chars for the key doesn't seem to be very big. Wher does it fail? Can you debug/back-trace it?
(gdb) r Starting program: /Users/mike/Developer/Parrot/Tests/mem_test Reading symbols for shared libraries . done
Program received signal EXC_BAD_ACCESS, Could not access memory.
0x00005f30 in string_transcode ()
(gdb) bt
#0 0x00005f30 in string_transcode ()
#1 0x00006de8 in string_compare ()
#2 0x000043e4 in find_bucket ()
#3 0x00004880 in hash_put ()
#4 0x00002998 in main ()
#5 0x000025a4 in _start (argc=1, argv=0xbffffdd4, envp=0xbffffddc) at /SourceCache/Csu/Csu-45/crt.c:267
#6 0x00002424 in start ()
And just as I was going to get started on t/src/string.t too.
I've made it a bit smaller: 65536.
This begs the questions:
What is the maximum hash key size? What is the largest STRING?
There are no limits except those imposed by UINTVAL (2^32-1) AFAIK.
Mike
leo
