I am using Eclipse 3.5 (galileo) and till yesterday it was working fine for my web application debugging. but since today, it has been acting weirdly. I have put number of break points and it does not stop at any .. ..
I tried these
- Cleaned workedspace
- Created the project from scratch (copied the exisiting source in it)
- re-installed the eclipse (unpacked from archive file)
and in all cases .. I got no success .. There were some moments when it stopped on some breakpoints .. but its upto eclipse .. if it would like it stops on breakpoints .. else it not ..
PLEASE PLEASE HELP Me - i can't go furterh without debugging and i don't want to add .. "system.out.println" everywhere.
The difference between <b>failure</b> and <b>success</b> is often being <b>right</b> and being <b>exactly right</b>.
Evidently either your debugger isn't connecting to the server or the server is referencing classes other than the ones that you have your breakpoints in. Since the internal debugger for Eclipse is the general remote debugger, maybe some of the hints in the link at the bottom of this thread might help.
Of course, you should be able to see your target application's threads in the Debug view. If you don't, you're DEFINITELY not connecting!
Customer surveys are for companies who didn't pay proper attention to begin with.
Joined: May 11, 2006
which links .. i can't see any link whcih can help me in this regard.
I can see the threads in debug view - but somehow breakpoints are not being hit. how come i make sure that the debugger is linked properly with classes source?
It do sometime stops on breakpoints - but i can never tell will it stop this time or not. I have system.out.println everywhere now :s
Are you sure the code with the breakpoints is being reached?
There were some moments when it stopped on some breakpoints .. but its upto eclipse .. if it would like it stops on breakpoints .. else it not ..
This is the kind of thing that happens when the source code in Eclipse doesn't match the compiled classes on app actually running under the debugger. When the program counter in the debugger hits a breakpoint, the debugger pauses and the debugging client is informed. However, when the source code isn't in sync, the displayed line-at-breakpoint isn't the actual line that triggered the breakpoint.