How to obtain a USEFUL logcat?

[Guest Frankish]

Is there a special way of getting a useful logcat for a specific issue? I know how to pull a logcat but just not sure if there is anything else to know?

[Guest galorin]

I don't know what the output for logcat looks like, but cat, >, |, grep, maybe sed, will be the tools I suspect you'd need to use. Seeing the work you've done, you are probably more than just passingly familiar with them. Reading logs is loads of fun, using Regular Expressions makes it doubly so... or would involving RegEx make it exponentially more fun?

[Guest Magnets]

I'm not sure what you're asking, but if you use Eclipse and DDMS you can filter by log levels and tags (click the green + button).

[Guest oh!dougal]

I'm not sure what you're asking, but if you use Eclipse and DDMS you can filter by log levels and tags (click the green + button).

"Dalvik Debug Monitor Service" (or so Google tells me)

In the “LogCat” tab, we have all messages from the device, most of them are incompressible, but here we can find Exceptions messages and Messages we add in the Android code using the Log.i(“Title”,”Message”) class to display “information” messages. If we want to display “Error” messages it would be something like Log.e(“Title Error”, “Error”).

http://www.brighthub.com/mobile/google-and...x#ixzz1EtWT3Twh

So you can add your own "log this" commands to your code to record stuff when you go through critical parts of your program ... is that what Frankish was meaning?

Is there a special way of getting a useful logcat for a specific issue? I know how to pull a logcat but just not sure if there is anything else to know?

Edited February 24, 2011 by oh!dougal