Since we are still undecided on whether to handle exceptions in VM code lazily or not to allow SOE at all in VM code, I have fixed ALexey's bug HARMONY-971 by precreating a default constructed SOE exception object ( used in situations like this..suspend_disable )and some more local rearranging. I did not want to leave the bug open since RI passes the scenario quite easily. But I suspect that we will need to do more work on SOE in VM code.
Thanks, Rana
On 7/25/06, Alexey Varlamov <[EMAIL PROTECTED]> wrote: > > [SNIP] > > > Shouldn't we care (even more) about kernel/classlib natives? I guess > > there are enough places lacking guard checks like " if > > (ExceptionOccured()) return 0;" > > > > BTW, the SOE machinery seems to be incomplete for this case, see > > HARMONY-971 issue. > > I think some issues could disappear if lazy exception creation is used > for SOE. Besides, it would be more reliable - in case we are really > tight on stack... > Pavel, is it possible without massive refactoring in exceptions > submodule ? > > [SNIP] > > -- > Alexey > >
