|
From: Nicholas N. <nj...@cs...> - 2005-03-15 19:40:18
|
On Tue, 15 Mar 2005, strk wrote: > $ valgrind --tool=addrcheck ./jtstest data1 > /dev/null > ... > ==26360== Invalid read of size 4 > ==26360== at 0x3489DE40: GC_push_all_eager (mark.c:1468) > ==26360== by 0x3489DEB1: GC_push_all_stack (mark.c:1521) > ==26360== by 0x348A6197: GC_push_all_stacks (pthread_stop_world.c:232) > ==26360== by 0x348A14D6: GC_default_push_other_roots (os_dep.c:1990) > ==26360== by 0x3489F563: GC_push_roots (mark_rts.c:643) > ==26360== by 0x3489E98E: GC_mark_some (mark.c:326) > ==26360== by 0x34895CCA: GC_stopped_mark (alloc.c:517) > ==26360== by 0x34896683: GC_try_to_collect_inner (alloc.c:364) > ==26360== by 0x34896EAD: GC_collect_or_expand (alloc.c:1007) > ==26360== by 0x34897069: GC_allocobj (alloc.c:1058) > ==26360== by 0x3489B68E: GC_generic_malloc_inner (malloc.c:134) > ==26360== by 0x3489C42E: GC_generic_malloc_many (mallocx.c:500) > ==26360== Address 0x9BDFF8CC is on thread 3's stack This might also be caused by the GC doing low-level things that Addrcheck doesn't expect. > ... > [ then hangs here ] That's not so good. Does it hang with --tool=none? If so, can you please file a bug report? Thanks. N |