search

mchr3k / org.intrace

Java tracing agent and live trace client
http://mchr3k.github.com/org.intrace/
73 stars 18 forks source link

Does not work in W7 if Eclipse path has embedded space(s) #27

Open robinH opened 11 years ago

robinH commented 11 years ago

My Eclipse happened to be installed in c:Program files/...

  1. Then when I Select Intrace as 'Java Application' I get an error, ( I can't remember exactly as it is now fixed), it ends with ... can't find c:Program. I fixed the problem by creating a new directory c:/ProgramFiles/Eclipse/.... (i.e. with no embedded spaces) and created another Eclipse installation.

Also, in the page "http://mchr3k.github.com/org.intrace/eclipse.html", it is not at all clear ( if you have never done it) just what has to done to make InTrace work. A blow-by-blow explanation would help. It seems the ordinary Run configuration is shared with InTrace, so .. Edit the usual run configuration to add the VM argument -javaagent:C:/fullpathto/intrace-agent.jar Ensure there is no space after the colon else it won't work! Also probably won't work if spaces in the path Select either the Package or the actual class to be traced. This action will cause the InTrace Run menu to have non-grey 'Java Application'. Click this. Then it should work.

mchr3k commented 11 years ago

As per the first screenshot on http://mchr3k.github.com/org.intrace/eclipse.html you should be able to launch your program directly from the InTrace menu.

Can you confirm if this menu is not working for you? If so, can you attach a screenshot?

robinH commented 11 years ago

Thanks for your interest.

I am just off snowbirding for 6 weeks, so I may not get back to this for a while. I temporarily fixed my problem (of tracing something) by compiling the Oracle demo Trace ( but they really didn't think thru classpath). Anyhow, I ran a trace that I could subsequently grep to get things of interest.

With InTrace, my main problem was that I could not get it to recognise my classes as needing instrumenation. The editing worked fine, but the most I ever got it to recognise was my main class. Any others would not show up even when using the advanced menu to list instrumented classes. If I used , then all the libraries java. sun.* would trace, but not my classes. I tried using full package + class and just class, but never more than my main would show up. Thread would sometimes be the only class instrumented.

To be clear, I could edit and add classes to the list in InTrace dialog and everything would appear to be normal, but they would not get recognised. No error messages at all, just no instrumentation.

I was all runing on JRE7 but then downloaded JRE6 and installed it telling Eclipse to configure as 1.6, but that did not seem to help.

While the above was I going on, I had no crashes, there may have been hangs but no exceptions, just no instrumentation.

The crash came with some particular setup that I can't recall the details.

It is hard to troubleshoot a new program when you don't know how it works when it is working.

Thanks again for your response

Robin Hayman

Robin & Diane Hayman 2375 Fifth Line road, Dunrobin (613)-832-3579

On 20/02/2013 4:47 PM, mchr3k wrote:

As per the first screenshot on http://mchr3k.github.com/org.intrace/eclipse.html you should be able to launch your program directly from the InTrace menu.

Can you confirm if this menu is not working for you? If so, can you attach a screenshot?

— Reply to this email directly or view it on GitHub https://github.com/mchr3k/org.intrace/issues/27#issuecomment-13858709.