| Problems when using Eclipse strictly as a debugger [message #77804] |
Fri, 18 July 2003 10:58 |
Eclipse User |
|
|
|
Originally posted by: nima.nortelnetworks.com
Hi folks,
Does anyone have a recipe to get Eclipse working properly with a s/w load
that is built outside of eclipse and needs to be debugged as a "Remote
Application"
Basically, my problem is that I can't get the debugger to recognize the
breakpoints that I set.
I have already built my s/w, with proper debug options, (class path is
different than source path), executed the application and have connected to
it using eclipse. I can get the thread list. I can find my source files and
set breakpoints, but they never get hit!
I read in the release notes that break points can only be set if the class
file is part of build class path of the project. I am not quite sure where
that is set either - I thought it would be the output folder in "Project
properties -> source" tab, but when I did that, it went and cleared all my
..class files! and then started to rebuild .Ouch! This is not my
intention. I want to be able to specify a source path and a prebuilt class
path and strictly use the debugger.
Here is basically what I have done:
- created a new project
- added a folder, that is a LINK to an existing filesystem folder.
- I can now view all my source files and set breakpoints
- Go to Run/Debug - enter all parameters for connection to the application
remotely and it successfully connects
- None of the breakpoints are hit!
I have played around with all kinds of properties - but I just can't get it
to work.
Any help is appreciated
cheers,
Nima
|
|
|
Powered by
FUDForum. Page generated in 0.03062 seconds
Home