Android adb命令logcat日志分析

一、简介

logcat 是 android 中的一个命令行工具，可以用于得到程序的log信息。下面介绍 adb logcat 中的详细参数命令以及如何才能高效的打印日志，或者把日志保存到我们指定的位置。

二、logcat命令

可以输入 adb logcat --help，查看一下一些简单的数据格式：

adb logcat --help

输出结果：

Usage: logcat [options] [filterspecs]

General options:
  -b, --buffer=<buffer>       Request alternate ring buffer(s):
                                main system radio events crash default all
                              Additionally, 'kernel' for userdebug and eng builds, and
                              'security' for Device Owner installations.
                              Multiple -b parameters or comma separated list of buffers are
                              allowed. Buffers are interleaved.
                              Default -b main,system,crash,kernel.
  -L, --last                  Dump logs from prior to last reboot from pstore.
  -c, --clear                 Clear (flush) the entire log and exit.
                              if -f is specified, clear the specified file and its related rotated
                              log files instead.
                              if -L is specified, clear pstore log instead.
  -d                          Dump the log and then exit (don't block).
  --pid=<pid>                 Only print logs from the given pid.
  --wrap                      Sleep for 2 hours or when buffer about to wrap whichever
                              comes first. Improves efficiency of polling by providing
                              an about-to-wrap wakeup.

Formatting:
  -v, --format=<format>       Sets log print format verb and adverbs, where <format> is one of:
                                brief help long process raw tag thread threadtime time
                              Modifying adverbs can be added:
                                color descriptive epoch monotonic printable uid usec UTC year zone
                              Multiple -v parameters or comma separated list of format and format
                              modifiers are allowed.
  -D, --dividers              Print dividers between each log buffer.
  -B, --binary                Output the log in binary.

Outfile files:
  -f, --file=<file>           Log to file instead of stdout.
  -r, --rotate-kbytes=<n>     Rotate log every <n> kbytes. Requires -f option.
  -n, --rotate-count=<count>  Sets max number of rotated logs to <count>, default 4.
  --id=<id>                   If the signature <id> for logging to file changes, then clear the
                              associated files and continue.

Logd control:
 These options send a control message to the logd daemon on device, print its return message if
 applicable, then exit. They are incompatible with -L, as these attributes do not apply to pstore.
  -g, --buffer-size           Get the size of the ring buffers within logd.
  -G, --buffer-size=<size>    Set size of a ring buffer in logd. May suffix with K or M.
                              This can individually control each buffer's size with -b.
  -S, --statistics            Output statistics.
                              --pid can be used to provide pid specific stats.
  -p, --prune                 Print prune rules. Each rule is specified as UID, UID/PID or /PID. A
                              '~' prefix indicates that elements matching the rule should be pruned
                              with higher priority otherwise they're pruned with lower priority. All
                              other pruning activity is oldest first. Special case ~! represents an
                              automatic pruning for the noisiest UID as determined by the current
                              statistics.  Special case ~1000/! represents pruning of the worst PID
                              within AID_SYSTEM when AID_SYSTEM is the noisiest UID.
  -P, --prune='<list> ...'    Set prune rules, using same format as listed above. Must be quoted.

Filtering:
  -s                          Set default filter to silent. Equivalent to filterspec '*:S'
  -e, --regex=<expr>          Only print lines where the log message matches <expr> where <expr> is
                              an ECMAScript regular expression.
  -m, --max-count=<count>     Quit after printing <count> lines. This is meant to be paired with
                              --regex, but will work on its own.
  --print                     This option is only applicable when --regex is set and only useful if
                              --max-count is also provided.
                              With --print, logcat will print all messages even if they do not
                              match the regex. Logcat will quit after printing the max-count number
                              of lines that match the regex.
  -t <count>                  Print only the most recent <count> lines (implies -d).
  -t '<time>'                 Print the lines since specified time (implies -d).
  -T <count>                  Print only the most recent <count> lines (does not imply -d).
  -T '<time>'                 Print the lines since specified time (not imply -d).
                              count is pure numerical, time is 'MM-DD hh:mm:ss.mmm...'
                              'YYYY-MM-DD hh:mm:ss.mmm...' or 'sssss.mmm...' format.
  --uid=<uids>                Only display log messages from UIDs present in the comma separate list
                              <uids>. No name look-up is performed, so UIDs must be provided as
                              numeric values. This option is only useful for the 'root', 'log', and
                              'system' users since only those users can view logs from other users.

filterspecs are a series of
  <tag>[:priority]

where <tag> is a log component tag (or * for all) and priority is:
  V    Verbose (default for <tag>)
  D    Debug (default for '*')
  I    Info
  W    Warn
  E    Error
  F    Fatal
  S    Silent (suppress all output)

'*' by itself means '*:D' and <tag> by itself means <tag>:V.
If no '*' filterspec or -s on command line, all filter defaults to '*:V'.
eg: '*:S <tag>' prints only <tag>, '<tag>:S' suppresses all <tag> log messages.

If not specified on the command line, filterspec is set from ANDROID_LOG_TAGS.

If not specified with -v on command line, format is set from ANDROID_PRINTF_LOG
or defaults to "threadtime"

2.1 adb logcat 命令格式

adb logcat [<option>] ... [<filter-spec>] ...
adb logcat [选项...] [过滤项...],

2.2 adb logcat 命令参数

2.3 adb logcat 日志缓冲区

Android 日志系统为日志消息保留了多个环形缓冲区，但并非多有的日志消息都会发送到默认的环形缓冲区。这里可以采用 logcat -b 命令查看设备的其他缓冲区：

2.4 adb logcat 格式化输出

使用 -v 命令来修改 log 的输出格式，以显示特定的元数据字段：

对于 -v 选项，如果需要查看线程区别使用 logcat -v threadtime 就可以了，其他日志基本也是少用的。

下面列举几种输出格式进行说明。

2.4.1 logcat -v brief

格式：

<priority>/<tag>(<pid>): <message>

示例：

D/TAG( 1785): Disconnected process message: 10, size: 0

2.4.2 logcat -v long

格式：

[ <datetime> <pid>:<tid> <priority>/<tag> ]

示例：

[ 08-28 22:39:39.974  1785: 1832 D/TAG ] Disconnected process message: 10, size: 0

2.4.3 logcat -v process

格式：

<priority>(<pid>) <message>

示例：

D( 1785) Disconnected process message: 10, size: 0 

2.4.4 logcat -v tag

格式：

<priority>/<tag>: <message>

示例：

D/TAG: Disconnected process message: 10, size: 0

2.4.5 logcat -v raw

格式：

<message>

示例：

Disconnected process message: 10, size: 0

2.4.6 logcat -v time

格式：

<datetime> <priority>/<tag>(<pid>): <message>

示例：

08-28 22:39:39.974 D/TAG( 1785): Disconnected process message: 10, size: 0

2.4.7 logcat -v threadtime

格式：

<datetime> <pid> <tid> <priority> <tag>: <message>

示例：

08-28 22:39:39.974  1785 1832 D TAG: Disconnected process message: 10, size: 0

2.5 adb logcat 日志级别

按日志级别过滤日志：

adb logcat <tag>[:priority]

tag 表示标签；priority 表示输出级别；

日志默认级别是 V，如果错误日志我们选择 E 就可以，Android 的日志分为如下几个优先级（priority）：

*可以是某个tag，如果没有指明，就表示所有。

三、adb logcat 示例

多数情况下，logcat命令参数都是组合使用。

3.1 adb logcat -b all -v threadtime --pid=4321 > /Users/xxx/logcat.log

将进程ID为4321的应用，所有缓冲区日志，按照 threadtime 格式输出到 logcat.log 日志文件中。

adb logcat -b all -v threadtime --pid=4321 > /Users/xxx/logcat.log

3.2 adb logcat -b all -c

将所有缓冲区日志清空。

adb logcat -b all -c

3.3 adb logcat -b all -d -v threadtime --pid=4321 -t 10

将进程ID为4321的应用，所有缓冲区日志，按照 threadtime 格式输出最新的10行日志（最多10行）。

adb logcat -b all -d -v threadtime --pid=4321 -t 10

四、Android 代码操作logcat日志

4.1 Android代码读取logcat日志

private void getLogcat(){
	String[] comand = new String[]{"logcat", "-b", "all", "-d", "-v", "threadtime", "--pid=4321", "-t", "10"};
    try{
        Process exec = Runtime.getRuntime().exec(comand);
        BufferedReader reader = new BufferedReader(new InputStreamReader(exec.getInputStream()));
        StringBuilder sb = new StringBuilder();
        String line;
        int i = 0;
        while ((line = reader.readLine()) != null) {
            sb.append(line).append("\r\n");
        }
        Log.i("TAG", "logcat content = " + sb.toString());
    }catch (Exception ex){
        Log.e("TAG", "Exception = " + ex.toString());
    }
}

4.2 Android代码实现将logcat日志输出到文件

public class LogcatProcesser {
	private Process logcatToFileProcess;

	/**
     * 获取日志输出文件
     */
	private String getLogcatFile(){
        String path = Environment.getExternalStorageDirectory().getAbsolutePath() + File.separator + "cwlogcat";
        File file = new File(path);
        if(!file.exists()){
            file.mkdirs();
        }
        return new File(file.getAbsolutePath() + File.separator + "cw_logcat.log").getAbsolutePath();
    }
    
	/**
     * 开启日志输出到文件
     */
	private void startLogcatToFile(){
        int pid = android.os.Process.myPid();
        String path = getLogcatFile();
        try{
            String[] cmds = new String[]{"logcat","-b", "all", "-v", "threadtime", "--pid=" + pid, "-f", path};
            if(logcatToFileProcess == null) {
            	// 持续将日志输出到日志文件中
                ProcessBuilder processBuilder = new ProcessBuilder(cmds);
                // 启动进程并重定向输出
                logcatToFileProcess = processBuilder.start();
                // 读取进程的错误流，以防止阻塞
                readStream(logcatToFileProcess.getErrorStream());
            }
        }catch (Exception ex){
            Log.e("TAG", "Exception = " + ex.toString());
        }
    }
    
    /**
     * 停止日志输出到文件
     */
	private void stopLogcatToFile(){
        try{
            if(logcatToFileProcess == null){
                return;
            }

            logcatToFileProcess.destroy();
            logcatToFileProcess = null;
        }catch (Exception ex){
            Log.e("TAG", "Exception = " + ex.toString());
        }
    }

	/**
	 * 读取进程的错误流
	 */
	private void readStream(final java.io.InputStream is) {
        new Thread(new Runnable() {
            @Override
            public void run() {
                try {
                    byte[] buffer = new byte[1024];
                    while (is.read(buffer) != -1) {
                        // 读取并忽略输入流中的数据
                    }
                    is.close();
                } catch (IOException e) {
                    Log.e("TAG", "Exception = " + ex.toString());
                }
            }
        }).start();
    }
}

文章来源地址https://www.toymoban.com/news/detail-848776.html

到了这里，关于Android adb命令logcat日志分析的文章就介绍完了。如果您还想了解更多内容，请在右上角搜索TOY模板网以前的文章或继续浏览下面的相关文章，希望大家以后多多支持TOY模板网！