I am sure that this was asked earlier, but I looked and did not see the final answer anywhere.
In eclipse, when debugging an Android program, if I throw an exception, Eclipse always wants to pull up the source file that contains the actual throw statement. I don’t have a source attached (and don’t want to), so it calls this "Source not found" window for android.jar every time I delete the exception.
I know that I can look at logcat to see the call stack, but is there a way to force eclipse to automatically open the file from which I raised an exception (the deepest file in the call stack for which the source exists) and not android.yar? It seems like little things, but instead, I was always stuck looking at this useless page every time I think that a reasonable solution would be to automatically extract the file from my source code that caused this problem. Instead, I should look at the call stack, go back to the java view, and find the offending file itself and open it, which is quite onerous.
Is there a way to improve my IDE setup, so I get more useful information right away than looking at this page of a useless class not found?
source
share