I did not dig the problem, -XDvm.use_finalizer is a valid option I usually use, think that assignee of H-2807 should find it out.
Aleksey. On 12/19/06, Geir Magnusson Jr. <[EMAIL PROTECTED]> wrote:
Aleksey Ignatenko wrote: > Yes, it's reproducible for me. > You should file jira on that issue. > Instead you should use -XDvm.use_finalizer=false option - everything works > fine with it. Is "vm.finalize" a real flag that doesn't work, or just not a real flag? geir > > Aleksey. > > > On 12/19/06, Vladimir Ivanov <[EMAIL PROTECTED]> wrote: >> >> DRLVM failed to start the eclipse 3.1.1 on the WinXP with - >> XDvm.finalize=false flag. The command is: >> %DRLVM%\bin\java -XDvm.assert_dialog=false -XDvm.finalize=false -cp >> "%ECLIPSE_HOME%\startup.jar" -Dosgi.install.area=%ECLIPSE_HOME%\ >> org.eclipse.core.launcher.Main -debug .options >> >> Output: >> C:\harmony_cc\trunk\cc>echo off >> Assertion failed: VM_Global_State::loader_env->finalizer_thread, file >> >> C:\harmony_cc\trunk\cc\projects\drlvm\trunk\vm\vmcore\src\init\finalize.cpp, >> >> line 370 >> >> This application has requested the Runtime to terminate it in an unusual >> way. >> Please contact the application's support team for more information. >> >> This application has requested the Runtime to terminate it in an unusual >> way. >> Please contact the application's support team for more information. >> 3 >> FAILED on New Java Class >> >> Could somebody reproduce/fix it? >> >> Thanks, Vladimir >> >> >
