Re: [Sablevm-developer] assert fails with new staging version

[Etienne G. <gag...@uq...>]

David B=E9langer wrote:
> yes, I still have it.  I built it clean from svn/staging, using the
> default options except enable debug and --with-threading=3Ddirect.

OK.  I analyzed the situation, and found out the bug.  It's not a
regression due to merging with newer classpath, as I thought it was.
It's an old, but hidden "false" bug that was exposed by the merge.

Mainly, when recursive initialization happens, the VM can actually
call a method on a yet uninitialized class.  The failing assetion was
thus a wrong assertion.  I have commented it, for now, as it would be
better to actually add an "in-progress-initialization" state and check
for this state in the assertion.

Of course, this only showed in debug mode, as it was an assertion bug
(and assertions are off in production mode).

So, you can consider the bug fixed in staging.

Etienne
--=20
Etienne M. Gagnon, Ph.D.             http://www.info.uqam.ca/~egagnon/
SableVM:                                       http://www.sablevm.org/
SableCC:                                       http://www.sablecc.org/