Hi,
Eclipse failed GC stress yesterday:
http://jikesrvm.anu.edu.au/cattrack/results/rvmx86lnx32b.anu.edu.au/stress/3781/gcstress/Opt_1/dacapo/eclipse/default/Output.txtLooking at the trace the object at 0x9d801e08 looks bogus, and this
seems to have also caused eclipse to wander into a bad monitor
exception. My only thought is that the object should once have been
valid and at some point this bogus object was introduced. Is there a
finite set of locations this could probably have happened and could we
introduce GC stress asserts to narrow it down? I'm thinking of places
where we move objects or modify references from one object to another.
Thanks,
Ian
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/_______________________________________________
Jikesrvm-core mailing list
Jikesrvm-core@...
https://lists.sourceforge.net/lists/listinfo/jikesrvm-core
