Question

I love when the Eclipse debugger halts the process and expands the Package Explorer to highlight the line in my source code when I cause a null pointer exception or other error, but I hate it when it attempts to do that for exceptions occurring within libraries for which I do not have linked source. In those cases it opens the Package Explorer deeply to that point (often deep within Android 2.1 SDK). This causes me to have to close the tree back up, and it shows an unhelpful tab for the corresponding class file that I also must close. Is it possible to retain the useful behavior only for exceptions happening in available source files?

Answer 1

There is a double arrow (<–>) on top of the package explorer. If you un-check this, Eclipse won’t focus the stack Package explorer when a resource is opened.

You can also choose what to show in the package explorer. In the package explorer menu (top right of the view, beside the double arrow), choose Filters… If you disable (select) Libraries from external, then the package explorer won’t show the libraries (and thus won’t expand them). However, this means that no libraries will be shown (not even ones with source). This isn’t exactly what you want, but it might help.