EVALUATION
After talking to Stefan on the phone I have a better understanding of what the
customers environment is.
This is only happening with debug vm, but preventing the debug vm from being
used to help debug another problem.
They are launching the vm from a native app, jlaunch.exe. They are unhappy about
the fact that the main thread launching the vm has its stack size set from the
executable and they cannot alter it ( as this later becomes a java thread ), see
bug 4689797. So they do not call JNI_CreateJavaVM from the initial thread but
from another with a differnet stack size.
Here's what is happening:
1) run jLaunch.exe, initial stack size X (taken from executable)
2) create thread T, stack size Y ( taken from -Xss parameter)
3) from thread T, call JNI_CreateJavaVM
4) assert
After looking at this more closely I do not see a problem with removing this assert in the case of is_nt(). If not premanently at least for a one off
debug build so that we can debug the real issue.
###@###.### 2004-08-11
=========================================
remove assert permanently in 1.4.2_07
###@###.### 2004-08-13