CODEWITHSUNDEEP
androideclipsedebuggingversion
MaiaVictor
MaiaVictor

Reputation: 53037

How to know which line the app crashed?

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?

Upvotes: 0

Views: 159

Answers (3)

MaiaVictor
MaiaVictor

Reputation: 53037

I was using the 'debug' option on Eclipse, which made it not show the error. Detaching the debug after the crash, or just running the application from the begin (without the debug options) shows the error. To find the line, filter your LogCat by application, make the app crash and, on the red text that will appear, look for your package name. And the of the error (expection) itself is on the beginning of that text.

Upvotes: 0

Seidr
Seidr

Reputation: 4936

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)

Upvotes: 2

Nahuelistico
Nahuelistico

Reputation: 42

Check Logcat filters (in Eclipse). Happens to me.

Upvotes: 1

Related Questions