Eclipse Community Forums - RDF feed
https://www.eclipse.org/forums/
Eclipse Community ForumsPassing VM Arguments To Profiled Application
https://www.eclipse.org/forums/index.php/mv/msg/33470/108513/#msg_108513
Originally posted by: downlodr417.msn.com
Hi there,
I feel like many others must have already encountered this, but I
haven't been able to find anything that seems to answer my question... I
am running Eclipse 3.3 and the latest version of TPTP (4.4?) I am
specifying VM arguments for a project in Eclipse (e.g.
-Djava.library.path=C:/somePath), and these arguments work properly in a
Run or Debug execution (I can print out the java.library.path system
property to verify this). However, when I run the same launch
configuration under Profiling mode, java.library.path is set to the
system's value; I assume that the VM arguments I'm specifying are in fact
being fed to some other application (I guess Hyades or something...?), and
that application is giving my app some default arguments. Anyway, I feel
like this is probably a really common need (to specify VM arguments for
the profiled application), so I must be missing something - could anyone
please enlighten me as to how to specify VM arguments for my application
under profiling mode? Thanks in advance!
- Daniel]]>2007-08-11T00:10:17-00:00Re: Passing VM Arguments To Profiled Application
https://www.eclipse.org/forums/index.php/mv/msg/33470/108692/#msg_108692
> Hi there,
>
> I feel like many others must have already encountered this, but I
> haven't been able to find anything that seems to answer my question... I
> am running Eclipse 3.3 and the latest version of TPTP (4.4?) I am
> specifying VM arguments for a project in Eclipse (e.g.
> -Djava.library.path=C:/somePath), and these arguments work properly in a
> Run or Debug execution (I can print out the java.library.path system
> property to verify this). However, when I run the same launch
> configuration under Profiling mode, java.library.path is set to the
> system's value; I assume that the VM arguments I'm specifying are in
> fact being fed to some other application (I guess Hyades or
> something...?), and that application is giving my app some default
> arguments. Anyway, I feel like this is probably a really common need
> (to specify VM arguments for the profiled application), so I must be
> missing something - could anyone please enlighten me as to how to
> specify VM arguments for my application under profiling mode? Thanks in
> advance!
>
> - Daniel
>
Daniel,
VM arguments should be specified in the "VM arguments" section of the
"Arguments" tab of the Launch Configuration of your application. I
tested this with the latest TPTP version and could not reproduce your
problem.
Can you please specify the exact version of your O/S, Eclipse, Java and
TPTP, and how exactly do you specify the VM arguments?
Thanks,
Asaf
--
Asaf Yaffe
Eclipse TPTP Committer, JVMTI Profiler]]>Asaf Yaffe2007-08-13T07:06:35-00:00Re: Passing VM Arguments To Profiled Application
https://www.eclipse.org/forums/index.php/mv/msg/33470/108850/#msg_108850
Originally posted by: downlodr417.msn.com
Hi Asaf,
Just to be clear, the process I'm following is "Run -> Profile...",
then clicking the Arguments tab, then specifying text in the "VM
Arguments" box, just as I normally do for debugging - it sounds to me like
this is what you're describing, but I just wanted to make sure there
wasn't some other VM Arguments configuration somewhere. :-P I'm running
Windows XP, Eclipse 3.3.0, currently using the 1.5.0_12 JRE, and I have
versions 4.4.0 of the TPTP Platform & Monitoring Tools and 4.3.0 of
Tracing & Profiling Tools (hopefully one of those has the version info
you're looking for). Thanks in advance for any help you can offer!
- Daniel]]>2007-08-13T15:52:55-00:00Re: Passing VM Arguments To Profiled Application
https://www.eclipse.org/forums/index.php/mv/msg/33470/108863/#msg_108863
Originally posted by: downlodr417.msn.com
Also, in regards to how I specify the arguments, I've been using something
like "-Djava.library.path=xyz" in order to set the system property
java.library.path to the value xyz. (No quotes on any of that...)
- Daniel]]>2007-08-13T15:54:51-00:00Re: Passing VM Arguments To Profiled Application
https://www.eclipse.org/forums/index.php/mv/msg/33470/108937/#msg_108937
Originally posted by: downlodr417.msn.com
Also also, I notice now that the value of java.library.path appears to be
roughly what I have in my Windows PATH environment variable, but with some
TPTP and Hyades stuff intermingled. Could it be that TPTP is adding its
own stuff to the path variable and clobbering my settings? Anyway, thanks
in advance for any advice you can offer...
- D]]>2007-08-13T21:11:29-00:00Re: Passing VM Arguments To Profiled Application
https://www.eclipse.org/forums/index.php/mv/msg/33470/109110/#msg_109110
Originally posted by: downlodr417.msn.com
Hi, just bumping this thread in hopes that it doesn't become forgotten; I
am hoping to use TPTP to help improve something I'm working on right now.
Please let me know what I might to do solve this problem with the VM
arguments - thanks!
- Daniel]]>2007-08-15T15:48:36-00:00Re: Passing VM Arguments To Profiled Application
https://www.eclipse.org/forums/index.php/mv/msg/33470/109946/#msg_109946
Originally posted by: chris.rendai.com
Hi Daniel,
Are you still having the same problem? I was having an issue when
launching the profiler and determined that variables within the VM
arguments were causing the issue.
- Chris Schmidt
Daniel wrote:
> Hi there,
>
> I feel like many others must have already encountered this, but I
> haven't been able to find anything that seems to answer my question... I
> am running Eclipse 3.3 and the latest version of TPTP (4.4?) I am
> specifying VM arguments for a project in Eclipse (e.g.
> -Djava.library.path=C:/somePath), and these arguments work properly in a
> Run or Debug execution (I can print out the java.library.path system
> property to verify this). However, when I run the same launch
> configuration under Profiling mode, java.library.path is set to the
> system's value; I assume that the VM arguments I'm specifying are in
> fact being fed to some other application (I guess Hyades or
> something...?), and that application is giving my app some default
> arguments. Anyway, I feel like this is probably a really common need
> (to specify VM arguments for the profiled application), so I must be
> missing something - could anyone please enlighten me as to how to
> specify VM arguments for my application under profiling mode? Thanks in
> advance!
>
> - Daniel
>]]>2007-08-24T03:46:03-00:00