Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Equinox » Eclipse Laucher and ini files(Having issues launching via org.eclipse.equinox.launcher and specifying an ini file)
Eclipse Laucher and ini files [message #805622] Fri, 24 February 2012 00:46 Go to next message
Brad Bode is currently offline Brad BodeFriend
Messages: 3
Registered: February 2012
Junior Member
Problem
I have a java product (deployed via a product file) that uses Jogl to make Open GL calls (it uses Worldwind). I need to debug OpenGL using gDebugger (an open source Open GL debugger) that will attach to the launched java application and keep track of all openGL calls. You cannot attach gDebugger to the EXE launcher otherwise this would be a simple issue.

How do you launch an eclipse product from the command line? I have tried
java -jar [plugins]/org.eclipse.equinox.launcher.jar --launcher.ini [pathToIni]


I have also tried specify the ECLIPSEHOME to point to my product directory (which contains the ini).

I have renamed the ini to config.ini (it is default to be named the same as the exe for the product.

And for clarity, I do NOT want to use the product exe at all. The launch must start by running java and passing in options.

I'd appreciate any help. I realize this is not the it is intended to be used, but for debugging purposes, this is what I have.
Re: Eclipse Laucher and ini files [message #805628 is a reply to message #805622] Fri, 24 February 2012 00:56 Go to previous messageGo to next message
Brad Bode is currently offline Brad BodeFriend
Messages: 3
Registered: February 2012
Junior Member
Another note... I also pulled the arguments out of the INI and ran them on the command line directly. Some of them worked, such as the -console option, but the java.library.path option seems to fail (JOGL is in the path, thus JOGL fails to load, thus worldwind doesn't work).

Thanks again
Re: Eclipse Laucher and ini files [message #805828 is a reply to message #805622] Fri, 24 February 2012 07:28 Go to previous messageGo to next message
Thorsten Meinl is currently offline Thorsten MeinlFriend
Messages: 85
Registered: July 2009
Member
You could add the options for debugger to you ini file and then still
start your product with the exe. But the java call

java -jar [plugins]/org.eclipse.equinox.launcher.jar ...

should also work. But note that the launcher adds some extra parameter
which are not in the ini such as the product name. I suggest you start
the exe and then check in the process list, which parameters have been
passed to the java call. Or you may have a look at the configuration
details somewhere in the help/about menu, they should also show all
arguments.



Am 24.02.2012 01:46, schrieb Brad Bode:
> Problem
> I have a java product (deployed via a product file) that uses Jogl to
> make Open GL calls (it uses Worldwind). I need to debug OpenGL using
> gDebugger (an open source Open GL debugger) that will attach to the
> launched java application and keep track of all openGL calls. You cannot
> attach gDebugger to the EXE launcher otherwise this would be a simple
> issue.
> How do you launch an eclipse product from the command line? I have tried
> java -jar [plugins]/org.eclipse.equinox.launcher.jar --launcher.ini
> [pathToIni]
>
> I have also tried specify the ECLIPSEHOME to point to my product
> directory (which contains the ini).
> I have renamed the ini to config.ini (it is default to be named the same
> as the exe for the product.
>
> And for clarity, I do NOT want to use the product exe at all. The launch
> must start by running java and passing in options.
>
> I'd appreciate any help. I realize this is not the it is intended to be
> used, but for debugging purposes, this is what I have.
Re: Eclipse Laucher and ini files [message #806294 is a reply to message #805828] Fri, 24 February 2012 19:54 Go to previous message
Brad Bode is currently offline Brad BodeFriend
Messages: 3
Registered: February 2012
Junior Member
I looked at the Help Menu as you suggested, tried adding missing options to my command line launch, and still had no luck. Rather than waste more time, I used a different open GL debugger that works simply.

So, for anyone looking to debug Open GL / JOGL that is embedded in an Eclipse RCP Product, I suggest the following:

1) Don't attempt to use gDebugger. It's too much of a pain to configure RCP to run via the commmand line (Without the Exe using java -jar ....).

2) Use glIntercept instead (I can't use links yet, otherwise I'd give you a link). You can simply put the glIntercept DLL into the same folder as the product EXE, run, and generate openGL log files. The log files can be used for diagnosis.

I hope this helps someone else.

Previous Topic:Making p2 more end user friendly
Next Topic:org.eclipse.osgi runtime temp files
Goto Forum:
  


Current Time: Wed Oct 20 01:58:31 GMT 2021

Powered by FUDForum. Page generated in 0.01977 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top