2007/5/23, Vladimir Ivanov <[EMAIL PROTECTED]>:
On 5/22/07, Alexey Varlamov <[EMAIL PROTECTED]> wrote:
> 2007/5/22, Vladimir Ivanov <[EMAIL PROTECTED]>:
> > On 5/22/07, Alexey Varlamov <[EMAIL PROTECTED]> wrote:
> > > 2007/5/22, Vladimir Ivanov <[EMAIL PROTECTED]>:
> > > > Hello,
> > > > I have a question about run of cunit tests: how I can specify
> > > > additional parameters for VM?
> > > > Now 'cunit.test.xml' does not support additional parameters (like
> > > > 'test.vmargs'). When I tried to add this option and specify gc_cc to
> > > > use I saw 'debug' window with log like:
> > > > [echo] ## Executing C unit test: test_java_attrs
> > > > [exec] Result: -1073741819
> > > > [echo] INFO: TEST test_jthread_get_priority start
> > > > [echo] ## TEST FAILED
> > > > [echo] ## Executing C unit test: test_java_basic
> > > > [exec] Result: -1073741819
> > > >
> > > > Is it expected behavior?
> > > >
> > > > As I see, the vm started as: JNI_CreateJavaVM(&GLOBAL_VM, &jni_env,
&args);
> > > > ,i.e. parameter like '-XX:vm.dlls=gc_cc.dll' is passed to vm.
> > > >
> > > > Command to run is (after update):
> > > > build.bat cunit.test -Dtest.vmargs=-XX:vm.dlls=gc_cc.dll
> > >
> >
> > > Wrapping the complex arg with quotes should do the trick:
> > > build.bat cunit.test -Dtest.vmargs="-XX:vm.dlls=gc_cc.dll"
> > > At least it works fine with other tests.
> >
> > Thanks, it works. But why VM crashed for non-quoted arg?
> Shell or some script down the execution path must be splitting args
> incorrectly, so VM actually receives bad arg.
Yes, it obvious. But I think our VM should report some error message
about incorrect args instead of crash.
thanks, Vladimir
Ah sorry, I just didn't noticed there is a hard crash. You are right,
please create a JIRA for this.
Thanks!
> >
> > >
> > > >
> > > > Note, command build.bat cunit.test -Dtest.vmargs=-showversion works
fine.
> > > >
> > > > thanks, Vladimir
> > > >
> > >
> >
>
