Debug


No Access to Eclipse Code During Debug Session

Eclipse will not provide debug access to its project libraries by default. As a result, when attempting to access an eclipse class, you will get an editor that displays the java byte-code contained in a class file. The editor header will read “The Jar of this class file belongs to container ‘Plug-in Dependencies’ which does not allow modifications to source attachments on its entries”.

To gain access to eclipse code go to: Preferences >Plug-in Development>Target Platform. You should have already downloaded the RCP target and the target location should be pointing to the appropriate directory. From the plug-in tab, enable the relevant unselected plug-ins (or enable them all). Click Apply and OK. This should provide you access to Eclipse code during debug sessions.

You may also gain access to eclipse code by selecting a predefined target with source. You will also be able to make this selection from Preferences >Plug-in Development>Target Platform.


Location of Eclipse log file

Errors generated during RCP development will be in the .log file (hidden file), under the .metadata folder of the relevant project in your workspace. That is, the log file will be under: Workspace/MyProject/.metadata/.log


You must be logged in to post a comment.