The short question is when using eclipse, how can I find out what line of my code triggered the error in cases where the stacktrace and debugger call stack don't reveal anything other than Android native methods.
I have been trying for a while to debug a program and have hit a bit of a wall. To give some background on the problem , my Android App crashes when I rotate my screen and I get the following stack trace:
From this stack trace, I can see that there is a Class Cast exception where a LinearLayout is trying to be cast as a Textview. What I don't know is where in the code this exception took place. Towards the bottom of the stack trace, the cause is just being explained when it cuts off with a "...55 more". So I started looking around for ways of extending the log cat and the only way I found only worked with extending the printStackTrace method on a caught exception. My next attempt was to run this on the debugger and examine the call stack when the exception was thrown. What I found looked like this:
both the call stack and the stack trace show the calls of several Android native methods but neither show what line in my code invoked the method. What I think is happening is that this code is being run from a handle or event queue. My question is in cases like this, is there a clever way to be able to tell what line of my code triggered this exception? Thanks in advance for help.