- This topic has 9 replies, 2 voices, and was last updated 20 years, 10 months ago by
.
-
Posts
-
Hi,
I recently downloaded a copy of the trial version of the IDE (version 2.8
beta) and installed it. However, after I started my evaluation through
building simple apps I tried to debug the code through setting a breakpoint.I set the breakpoint, but when I tried to run the app through the debugger, it appeared to stop doing anything (not even entering my source code), but still be running. It didn’t hang, it just
appeared to do nothing.In the debug window, the resume button is greyed out, only suspend and terminate are available. The debug view indicates that all system threads are running.
At one point all I had was a class with only a main method and a System.out.println(), but still nothing.
I have since removed MyEclipse IDE from my desktop and tried again, this time it worked. So, there is something in this IDE plugin preventing debugging in a normal manner.
Can you tell me if there are any issues debugging in eclipse while using
the IDE plugin software? Is there any settings that I need to make to allow debugging to work? Most puzzling -> please help!Thanks,
Stuart
Hi Stuart,
I have since removed MyEclipse IDE from my desktop and tried again, this time it worked.
So is it working, or not working now?
So, there is something in this IDE plugin preventing debugging in a normal manner.
What version of Eclipse are you using? What version of JDK? What are you trying to debug? What application server are you using? How many fingers am I holding up?
Can you tell me if there are any issues debugging in eclipse while using
the IDE plugin software?If its configured wrong, sure, there are lots of issues 😀
Is there any settings that I need to make to allow debugging to work?
You need a few things for successful debugging: http://www.myeclipseide.com/FAQ+index-myfaq-yes-id_cat-14.html#100
>>So is it working, or not working now?
Yes it is working 🙂>>What version of Eclipse are you using? What version of JDK? What are you trying to debug? What application server are you using? How many fingers am I holding up?
Eclipse 2.1.3
JDK 1.3
Just trying to debug an application (non web-based)
No application server being used
eh…..4 fingers 🙂Any thoughts?
Oh, I should also add to this part:
>>So is it working, or not working now?
Where I said………”Yes it is working”However, I can only get the eclipse debugger to work when I uninstall MyEclipseIDE 🙁 I want MyEclipse IDE and a debugger to work! 🙂
However, I can only get the eclipse debugger to work when I uninstall MyEclipseIDE
Hmm that is weird… I don’t know why this would effect it at all. Can you explain to us in detail what happens? For example, when its just Eclipse, you click Debug > Run As > Application, and everything works, and then when MyEclipse is installed, you click Debug > Run As> APplication and none of your breakpoints are hit?
Is there a reason you are using JDk 1.3? Can you upgrade to the most recent JDK release?
>>For example, when its just Eclipse, you click Debug > Run As > Application, and everything works, and then when MyEclipse is installed, you click Debug > Run As> APplication and none of your breakpoints are hit?
That is exactly the behaviour I have.
>>Is there a reason you are using JDk 1.3? Can you upgrade to the most recent JDK release?
Legacy unfortunately. We are tied to 1.3 for the moment. However, I do have 1.4 installed on my computer as well, so for a test I selected 1.4 as my JRE in Eclipse, but that didn’t make any difference unfortunately.
The application code I have that I am trying to debug is simply:
public class TempClass {
public static void main(String[] args) {
System.out.println(“This is a temp test”);
}}
I have set my breakpoint on the System.out, but it never hits that.
Thanks so far with your swift responses. I am heading off home so I will pick up any thoughts you may have tomorrow.
Stuart
Stuart,
I’ve talked this through with the team and we’ve ALL tried to reproduce this and not had any luck. The only difference I can think of us that most of us are using the newest 1.4.1 or 1.4.2 releases of the JDK, what version of JDK 1.4.1 did you test with? (There were like 10 sub releases I think).We are thinking that this might be a configuration issue on your end, but we don’t know if we have enough info to run with yet. Out of curisotiry, under Window > Preferences > Java > Compiler what compliance level do you have the compiler set to? Just double check that its 1.3… also are your compiler settings leaving in all the debugging information in the class files, or stripping it?
Also check your Project proeprties to make sure you haven’t set custom compiler settings JUST for that project with the breakpoint issues.
Hi Riyad,
Sorry for the delay getting back to you. I am currently running with JDK 1.4.0_01, but I get the same behaviour running under 1.3.1_12. I checked the compliance level and it is 1.3.
I haven’t went out of my way to change any compiler settings so it will be running with the default Eclipse / MyEclipse IDE settings.
It isn’t obvious like debugging is not available in the trial version is it?
This is a bit of a pain as I really like what the IDE offers and I am pushing to purchase a full version but I would like to know why this debugger is not moving.
To summarise the behaviour: with MyEclipse IDE installed debugger launches, creates threads and does nothing with the code. Run the code in non-debug mode and it is fine.
Uninstall the IDE and just use Eclipse plain and simple, debugger launches, creates threads to run and steps into the program stopping at any break points set.
Very odd, any more thoughts?
Thanks,
Stuart
I am currently running with JDK 1.4.0_01
I don’t know if this might be the problem… I know we’ve fixed a *vast* majority of debugging problems before by having people just upgrade their JDK.
It isn’t obvious like debugging is not available in the trial version is it?
I wish it were, but we don’t do anything fancy in the trial. It just nags you when you don’t register after 30 days.
This is a bit of a pain
I agree, this is a huge PIA.
To summarise the behaviour: with MyEclipse IDE installed debugger launches, creates threads and does nothing with the code.
You mean that no breakpoints are hit, OR do you mean that the program doesn’t execute at all and just sits there doing nothing? Have you tried switching to the debug view and clicking the Play button? Something weird I noticed with Eclipse 3.0 in debug mode on a project I’m working on now, is that it immediately halts inside of the FileOutputStream class twice, so I have to click “Continue” twice IMMEDIATELY after starting an application in debug mode… I wonder if its the same problem for you?
