Now, when we invoke Step Into on a code which is included in this preference it will be treated as Step Over - we won't see the "Source not found" message any more.
This is a blog of Eclipse enthusiasts from Poznań (Poland) who would like to share their knowledge of Eclipse. We work for the IBM Support Center for Eclipse at Poznań University of Technology.
Tuesday, February 24, 2009
Eclipse Debugger, part VII
Today I have discovered very nice feature of Eclipse Debugger - it is possible to get rid of the "Source not found" message while debugging. One obvious solution is to add the source to the code that we want to debug, but there are times when we don't have access to the sources of some libraries. In this situation we can use Step Filtering preference:

Now, when we invoke Step Into on a code which is included in this preference it will be treated as Step Over - we won't see the "Source not found" message any more.
Now, when we invoke Step Into on a code which is included in this preference it will be treated as Step Over - we won't see the "Source not found" message any more.
Yes, step filtering is great!
ReplyDeleteI've contributed an enhancement which filters mundane getters and setters. Unfortunately, it won't make it into 3.5, but it can be added separately.