Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m debugging an app in a real device and Eclipse. Certain feature makes it crash. There is no error on LogCat. I’ve managed to find which line it crashed in a similar situation by writting Log.v in many lines until I found which Log.v didn’t show up. Isn’t there a better solution?
You could use the Debugging feature in Eclipse – it allows you to break the program flow on the occurrence of an exception (Run As -> Debug).
This will allow you to inspect the current local variables / call stack to further diagnose why the exception occurs.
p.s. One other method I use when hunting down an odd crash is to dump the full LogCat via the ‘adb’ CLI tool, and inspect it in a text editor. Sometimes the LogCat display in Eclipse can go a bit.. weird..especially if you’ve been connecting / disconnecting your device while developing (without closing Eclipse)