| Native Launcher Behavior Change in 3.4? [message #327676] |
Mon, 28 April 2008 15:13  |
Eclipse User |
|
|
|
Hi There,
We are trying to release a milestone based on Eclipse 3.4M6a, and I have=
=
run into an interesting issue. We have our own command line application=
=
that we run using the eclipse launcher like so:
path_to\eclipse\eclipsec.exe -nosplash -application id.of.our.App
This all works fine in Eclipse 3.3. However, in Eclipse 3.4M6a if our =
application returns a non-zero exit status (as is the case for invalid =
arguments, or a general failure of any sort), the Eclipse launcher throw=
s =
up a huge dialog with message indicating that the "JVM terminated. Exit =
=
code=3D2", and then proceeds to dump all of the command line args, etc. =
Now =
I can't tell if this is Java crashing, or if this is new behavior for th=
e =
launcher. I cannot find a Java crashlog, and if I run the same code in =
a =
runtime Eclipse it terminates without major failures so I think this is =
=
launcher-related. Can someone help me out here? As I said, I can't see=
=
that it would be Java crashing, unless something major has changed betwe=
en =
3.3 and 3.4. If this is the new, default behavior - isn't it a little =
extreme to show this dialog whenever a non-zero exit status occurs?? If=
=
this is the new way of handling non-zero exit status, how can I suppress=
=
this dialog? I tried --launcher.suppressErrors, but it just spits the =
same information onto stderr.
Thanks,
Mark.
|
|
|
| Re: Native Launcher Behavior Change in 3.4? [message #327679 is a reply to message #327676] |
Mon, 28 April 2008 17:06  |
| Eclipse User |
|
|
|
Looks like there is a bit of an explanation here:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=3D209080
I guess this is being looked at for M7?
M.
On Mon, 28 Apr 2008 15:13:13 -0400, Mark Melvin <mark.melvin@onsemi.com>=
=
wrote:
> Hi There,
>
> We are trying to release a milestone based on Eclipse 3.4M6a, and I ha=
ve =
> run into an interesting issue. We have our own command line applicati=
on =
> that we run using the eclipse launcher like so:
>
> path_to\eclipse\eclipsec.exe -nosplash -application id.of.our.App
>
> This all works fine in Eclipse 3.3. However, in Eclipse 3.4M6a if our=
=
> application returns a non-zero exit status (as is the case for invalid=
=
> arguments, or a general failure of any sort), the Eclipse launcher =
> throws up a huge dialog with message indicating that the "JVM =
> terminated. Exit code=3D2", and then proceeds to dump all of the comma=
nd =
> line args, etc. Now I can't tell if this is Java crashing, or if this=
=
> is new behavior for the launcher. I cannot find a Java crashlog, and =
if =
> I run the same code in a runtime Eclipse it terminates without major =
> failures so I think this is launcher-related. Can someone help me out=
=
> here? As I said, I can't see that it would be Java crashing, unless =
> something major has changed between 3.3 and 3.4. If this is the new, =
=
> default behavior - isn't it a little extreme to show this dialog =
> whenever a non-zero exit status occurs?? If this is the new way of =
> handling non-zero exit status, how can I suppress this dialog? I trie=
d =
> --launcher.suppressErrors, but it just spits the same information onto=
=
> stderr.
>
> Thanks,
> Mark.
|
|
|
Powered by
FUDForum. Page generated in 0.06440 seconds
Home