| Java initial stack size for running a native library [message #203390] |
Wed, 04 April 2007 23:10  |
Eclipse User |
|
|
|
Originally posted by: jmarvin.totimm.com
I need to change the Java initial stack size for running a native library
within our RCP application.
Currently we export the RCP app and use a Java modified with MS SDK's
editbin whereby the initial stack size is changed.
Eclipse runs using the same Java, but running the RCP app within Eclipse
doesn't use the changed initial stack size, so the library fails.
I have tried setting the initial stack size within the launch
configuration for VM arguments using -Xiss1000000 (and various other
numbers like 1m), but that doesn't seem to fix it.
I've read stuff about the primordial thread not being changeable per the
initial stack size and being required to use the editbin way if you can't
spawn a thread. I've verified that if I stuff the the native library's
initialization code into a new thread the stack increase is then
recognized and it initializes, however our SWT interaction immediately
breaks and we get a message like "invalid thread".
I run my RCP application successfully outside Eclipse like so:
$JAVA_HOME/bin/java.exe -classpath startup.jar
org.eclipse.core.launcher.Main
Is the above running the application in a thread other than the
primordial? If so, how can I get Eclipse to launch it the same way for
debugging/development?
Is there a place in a typical RCP app to encapsulate the entire
application in another thread?
Thanks,
Jay Marvin
|
|
|
|
Powered by
FUDForum. Page generated in 0.08938 seconds
] 
Search
Help
Register
Login
Home
