score:9

Accepted answer

the only way i know of to filter the stack trace view is via mylyn. if you have an active mylyn task, and you click the "focus on active task (experimental)" button in the debug view, then the stack trace will be filtered to only show those methods that are in the current task's context.

in this case, you wouldn't be filtering certain items from the stack trace; rather, everything would be out by default, and only certain items would be displayed (those in the task context).

you can look at this answer for more about mylyn.

score:13

preparation: you can use step filters as described here. then whenever you step-debug through your code, it will not jump into excluded packages or classes, e.g. from the jdk or some frameworks like hibernate or spring. but this is just a prerequisite.

solution: the stacktrace still contains frames from those those packages. in order to filter out those as well, you need to patch the eclipse jdt debug ui plugin. someone else has done that already for older eclipse releases up to indigo. because i was curious if i could get it running in the current release luna 4.4.1 as well, i recreated the other guy's changes and pushed the debug view + stack filter plug-in to github including a download link to the patched plugin. so if you are also on 4.4.1, you are lucky and do not need to patch and compile anything by yourself. just use my version. otherwise please clone my repo and look at the changes, then apply them to the plugin version of your choice.


Related Query

More Query from same tag