android开发用logcat跟踪错误

为什么80%的码农都做不了架构师？>>>   

android.util.Log

Generally, use the Log.v() Log.d() Log.i() Log.w() and Log.e() methods.

The order in terms of verbosity, from least to most is ERROR, WARN, INFO, DEBUG, VERBOSE. Verbose should never be compiled into an application except during development. Debug logs are compiled in but stripped at runtime. Error, warning and info logs are always kept.

Tip: A good convention is to declare a TAG constant in your class:

private static final String TAG = "MyActivity";

and use that in subsequent calls to the log methods.

Tip: Don't forget that when you make a call like

Log.v(TAG, "index=" + i);

that when you're building the string to pass into Log.d, the compiler uses a StringBuilder and at least three allocations occur: the StringBuilder itself, the buffer, and the String object. Realistically, there is also another buffer allocation and copy, and even more pressure on the gc. That means that if your log message is filtered out, you might be doing significant work and incurring significant overhead.

Summary

Constants
int	ASSERT	Priority constant for the println method.
int	DEBUG	Priority constant for the println method; use Log.d.
int	ERROR	Priority constant for the println method; use Log.e.
int	INFO	Priority constant for the println method; use Log.i.
int	VERBOSE	Priority constant for the println method; use Log.v.
int	WARN	Priority constant for the println method; use Log.w.

转载于:https://my.oschina.net/durong/blog/115828