一个能让你了解所有函数调用顺序的Android库!
鹏必生辉
7年前
<p>背景：当项目代码量很大的时候，或者你作为一名新人要快速掌握代码的时候，给函数打上log，来了解代码执行逻辑，这种方式会显然成本太大，要改动项目编译运行，NO！太耗时；或者你想debug的方式来给你想关注的几个函数，来了解代码执行逻辑，NO！因为你肯定会漏掉函数；也许你可以固执的给你写的项目打满log说这样也行，但是你要知道你方法所调用的jdk的函数或者第三方aar或者jar再或者android sdk中的函数调用顺序你怎么办，还能打log吗？显然不行吧，来~这个项目给让可以让你以包名为过滤点过滤你想要知道所有函数调用顺序。</p> <h2>1. 效果奉上</h2> <p><img src="https://simg.open-open.com/show/c75cca432cbda96c826cd4662fa09a01.gif"></p> <p>动作简介：首先点击MainActivity的自定义MyTextView然后进入SecondActivity再点击textview之后finish跳转回MainActivity</p> <p>下面是库处理过所得到的函数调用顺序 order.txt 文件（我这里屏蔽了jdk函数，第三方库函数，以及android sdk中函数，换句话说我就保留了我自己包名中的函数顺序）</p> <pre> <code class="language-java">832 ent 67593 .....com.zjw.appmethodorder.MainActivity.onClick (Landroid/view/View;)V MainActivity.java 832 ent 99956 ..........com.zjw.appmethodorder.MainActivity.onPause ()V MainActivity.java 832 ent 99970 ...........com.zjw.appmethodorder.BaseActivity.onPause ()V BaseActivity.java 832 ent 100472 ............com.zjw.appmethodorder.BaseActivity.baseOnPause ()V BaseActivity.java 832 ent 128540 ........com.zjw.appmethodorder.SecondActivity.<init> ()V SecondActivity.java 832 ent 128562 .........com.zjw.appmethodorder.BaseActivity.<init> ()V BaseActivity.java 832 ent 213911 ........com.zjw.appmethodorder.SecondActivity.onCreate (Landroid/os/Bundle;)V SecondActivity.java 832 ent 213928 .........com.zjw.appmethodorder.BaseActivity.onCreate (Landroid/os/Bundle;)V BaseActivity.java 832 ent 258414 ..........com.zjw.appmethodorder.BaseActivity.baseOnCreate ()V BaseActivity.java 832 ent 1440503 .........com.zjw.appmethodorder.SecondActivity.onResume ()V SecondActivity.java 832 ent 1440563 ..........com.zjw.appmethodorder.BaseActivity.onResume ()V BaseActivity.java 832 ent 1445675 ...........com.zjw.appmethodorder.BaseActivity.baseOnResume ()V BaseActivity.java 832 ent 2954291 .................com.zjw.appmethodorder.MyTextView.onWindowVisibilityChanged (I)V MyTextView.java 832 ent 3065664 ........com.zjw.appmethodorder.MainActivity.onStop ()V MainActivity.java 832 ent 3065701 .........com.zjw.appmethodorder.BaseActivity.onStop ()V BaseActivity.java 832 ent 3069155 ..........com.zjw.appmethodorder.BaseActivity.baseOnStop ()V BaseActivity.java 832 ent 3139519 .......com.zjw.appmethodorder.SecondActivity.click (Landroid/view/View;)V SecondActivity.java 832 ent 3146300 ........com.zjw.appmethodorder.SecondActivity.finish ()V SecondActivity.java 832 ent 3183478 ..........com.zjw.appmethodorder.SecondActivity.onPause ()V SecondActivity.java 832 ent 3183498 ...........com.zjw.appmethodorder.BaseActivity.onPause ()V BaseActivity.java 832 ent 3183843 ............com.zjw.appmethodorder.BaseActivity.baseOnPause ()V BaseActivity.java 832 ent 3209420 ........com.zjw.appmethodorder.MainActivity.<init> ()V MainActivity.java 832 ent 3209438 .........com.zjw.appmethodorder.BaseActivity.<init> ()V BaseActivity.java 832 ent 3283359 ........com.zjw.appmethodorder.MainActivity.onCreate (Landroid/os/Bundle;)V MainActivity.java 832 ent 3283378 .........com.zjw.appmethodorder.BaseActivity.onCreate (Landroid/os/Bundle;)V BaseActivity.java 832 ent 3330938 ..........com.zjw.appmethodorder.BaseActivity.baseOnCreate ()V BaseActivity.java 832 ent 4363295 .....................com.zjw.appmethodorder.MyTextView.<init> (Landroid/content/Context;Landroid/util/AttributeSet;)V MyTextView.java 832 ent 4436094 ..................com.zjw.appmethodorder.MyTextView.onFinishInflate ()V MyTextView.java 832 ent 4449689 .........com.zjw.appmethodorder.MainActivity.initView ()V MainActivity.java 832 ent 4539427 .........com.zjw.appmethodorder.MainActivity.onResume ()V MainActivity.java 832 ent 4539467 ..........com.zjw.appmethodorder.BaseActivity.onResume ()V BaseActivity.java 832 ent 4543597 ...........com.zjw.appmethodorder.BaseActivity.baseOnResume ()V BaseActivity.java 832 ent 4917854 .................com.zjw.appmethodorder.MyTextView.onAttachedToWindow ()V MyTextView.java 832 ent 4918658 .................com.zjw.appmethodorder.MyTextView.onWindowVisibilityChanged (I)V MyTextView.java 832 ent 5090653 ...................................com.zjw.appmethodorder.MyTextView.onMeasure (II)V MyTextView.java 832 ent 5355203 ..................................com.zjw.appmethodorder.MyTextView.onMeasure (II)V MyTextView.java 832 ent 5456681 .......................................com.zjw.appmethodorder.MyTextView.onSizeChanged (IIII)V MyTextView.java 832 ent 5467577 ....................................com.zjw.appmethodorder.MyTextView.onLayout (ZIIII)V MyTextView.java 832 ent 5876623 ...........................................com.zjw.appmethodorder.MyTextView.onDraw (Landroid/graphics/Canvas;)V MyTextView.java 832 ent 6121967 ........com.zjw.appmethodorder.SecondActivity.onStop ()V SecondActivity.java 832 ent 6121986 .........com.zjw.appmethodorder.BaseActivity.onStop ()V BaseActivity.java 832 ent 6123689 ..........com.zjw.appmethodorder.BaseActivity.baseOnStop ()V BaseActivity.java 832 ent 6127522 ........com.zjw.appmethodorder.SecondActivity.onDestroy ()V SecondActivity.java 832 ent 6127679 .........com.zjw.appmethodorder.BaseActivity.onDestroy ()V BaseActivity.java 832 ent 6133301 ..........com.zjw.appmethodorder.BaseActivity.baseOnDestroy ()V BaseActivity.java</code></pre> <p>OK！发现是不是很炫酷啊，下面来介绍该库的原理（求star!!!）</p> <h2>2 原理</h2> <p>本库其实并没有什么黑科技，本库也没有java代码，核心就是2个build.gradle中的task。首先，原理就是基于android sdk中提供的工具----traceview，和dmtracedump。traceview会生成.trace文件，该文件记录了函数调用顺序，函数耗时，函数调用次数等等有用的信息。而dmtracedump 工具就是基于trace文件生成报告的工具，具体用法不细说。dmtracedump 工具大家一般用的多的选项就是生成html报告，或者生成调用顺序图片（看起来很不直观）。首先说说为什么要用traceview，和dmtracedump来作为得到函数调用顺序的，因为这个工具既然能知道cpu执行时间和调用次数以及函数调用树（看出函数调用顺序很费劲）比如android studio是这样呈现.trace文件的解析视图的</p> <p><img src="https://simg.open-open.com/show/7de54e1bafc46943c2ce78b158f77251.png"> 或者这样的</p> <p><img src="https://simg.open-open.com/show/2d02c0f377b109fb89e85f2e95b086b9.png"> (上面这张图是网上找的，侵删) 用上面这2个图发现你要清晰知道函数调用看懂了才是见鬼了。或者使用dmtracedump 工具解析生成的html长下面这样（dmtracedump 生成图片就不说了 生成出的图片也根本看不出顺序这个就略过了）</p> <p><img src="https://simg.open-open.com/show/ea4cc0f6955c2913881fc833167b2dcb.png"> 一开始我以为 Method 序列号有戏于是乎冲动的我把带序号的东西内容复制出来写了一个脚本对他们进行排序代码如下：</p> <pre> <code class="language-java">import java.io.BufferedReader; import java.io.FileReader; import java.io.IOException; import java.util.ArrayList; import java.util.Arrays; import java.util.Collections; import java.util.regex.Matcher; import java.util.regex.Pattern; public class Sort implements Comparable<Sort> { static String uri = "D:/Application/eclipse/javaworkspace/Test/src/JB/1.text"; String str = ""; String content = ""; public Sort(String str,String content) { super(); this.str = str; this.content = content; } public static void main(String[] args) throws IOException { // TODO Auto-generated method stub ArrayList<Sort> list = new ArrayList<>(); BufferedReader in = new BufferedReader(new FileReader(uri)); String a = ""; while ((a = in.readLine()) != null) { //System.out.println(Long.valueOf(getIndexStr(a))); if(a.contains("com.zjw.appmethodorder")){ list.add(new Sort(getIndexStr(a),a)); } } Collections.sort(list); for (Sort sort : list) { System.out.println(sort.content); } } public static String getIndexStr(String str) { String regEx = "(?<=\[)(\S+)(?=\])";// 匹配[]中的数字 Pattern p = Pattern.compile(regEx); Matcher m = p.matcher(str.trim()); while (m.find()) { return m.group().trim(); } return ""; } @Override public int compareTo(Sort o) { // TODO Auto-generated method stub //return 0; return (int) (Long.valueOf(str) - Long.valueOf(o.str)); } }</code></pre> <p>结果发现过滤后的东西序列号是按顺序的但是并不是代码执行的逻辑顺序。我擦怎么办，工具代码也写了，居然不是我想要的结果，好在花了一些时间发现dmtracedump -ho 选项，经过研究发现，这玩意输出的内容居然是按逻辑顺序从上到下的，于是基于这一点我写一个项目，其实核心就是2个task完成了了解所有函数调用顺序的目的。</p> <pre> <code class="language-java">//核心任务：在captures文件目录下输出 基于最新.trace文件的函数调用信息的txt版本 //说明：dmtracedump 为 android sdk自带工具，要执行dmtracedump命令则需要先添加环境变量 task AppOutPutMethodOrder() { doLast { def capturesDirPath = project.getProjectDir().getParentFile().path + File.separator + "captures"; def capturesDir = file(capturesDirPath); def traceType = "trace" if (!capturesDir.exists() || !capturesDir.canRead()) { return } def map = new TreeMap<Long, String>( new Comparator<Long>() { public int compare(Long obj1, Long obj2) { return obj2.compareTo(obj1); } }); //遍历拿到trace 文件名 然后排序 找到最大时间数的trace就是最新的文件，拿到字符串 capturesDir.list(new FilenameFilter() { @Override boolean accept(File dir, String name) { if (name.contains(traceType)) { def substring = name.substring(name.length() - 22, name.length() - 6).trim() String regEx = "[^0-9]" Pattern p = Pattern.compile(regEx) Matcher m = p.matcher(substring) def time = m.replaceAll("").trim() map.put(Long.parseLong(time), name) } return false } }) def lastTraceName = ""; Set<Long> keySet = map.keySet(); Iterator<Long> iterator = keySet.iterator(); while (iterator.hasNext()) { Long key = iterator.next(); lastTraceName = map.get(key); break; } def tracePath = capturesDirPath + File.separator + lastTraceName println "===== tracePath is ${tracePath} ==========" def orderPath = capturesDirPath + File.separator + "base_order.txt" def orderFile = file(orderPath) if(orderFile.exists()){ orderFile.write("") } Runtime runtime = Runtime.getRuntime(); //说明：dmtracedump 为 android sdk自带工具，要执行dmtracedump命令则需要先添加环境变量 def baseComand = "dmtracedump -ho " + tracePath + " >> " + orderPath def command = "" String[] cmdArray = null; String osName = System.getProperty("os.name"); String osNameMatch = osName.toLowerCase(); if(osNameMatch.contains("windows")) { command = "cmd /c start /b "+baseComand; }else { cmdArray = ["bash", "-c", baseComand]; } try { if (cmdArray != null) { runtime.exec(cmdArray); } else { runtime.exec(command); } } catch (Exception e) { println "=====Exception: ${e.getCause()} ==========" } } } //这里AppFilterMethodOrder 任务其实也不需要 执行找到 captures 目录找到 base_order.txt //用Notepad++ 使用正则 先过滤 带 xit 的行 （我们只关注ent 行就行，ent代表进入执行函数 xit代表退出函数）再过滤掉你不关心的包名 // Notepad++ 中过滤将会使用到的命令行如下 //^.*xit.*$ //去除掉 含有 xit 字符串的行 然后替换为空 // ^((?!XXX).)*$ //去除不包含XXX的行 然后替换为空 //^s+ //合并空行 然后替换为空 task AppFilterMethodOrder(){ doLast{ def capturesDirPath = project.getProjectDir().getParentFile().path + File.separator + "captures"; def orderPath = capturesDirPath + File.separator + "base_order.txt" if(!file(orderPath).exists()){ return } BufferedReader inputStream = new BufferedReader(new FileReader(orderPath)); def filterOrderPath = new File(capturesDirPath + File.separator + "order.txt") if (!filterOrderPath.exists()){ filterOrderPath.createNewFile(); }else { filterOrderPath.write("") } String content ; while ((content = inputStream.readLine()) != null) { if(content.contains(" ent ") //com.zjw.appmethodorder 这里可以修改成你想要留下的包名对应的函数调用信息 && content.contains("com.zjw.appmethodorder") ){ filterOrderPath .append(content+"n") } } } }</code></pre> <h2>3.如何使用</h2> <p>讲了一堆原理我们来说说这个库怎么用吧。</p> <p>首先编译运行项目，然后点击下图的时钟（这是使用工具打trace start 和 end）进行操作，可以参考上文所说的动作简介（记住你操作想想你的生命周期函数调用顺序，待会可以和生成的captures目录下base_order.txt或者生成的order.txt中的函数顺序做做对比）然后再点一次下图那个时钟。还有一种记录trace start 和 end的方式就是在修改代码,即使用 android.os.Debug.startMethodTracing(); 和 android.os.Debug.stopMethodTracing(); <img src="https://simg.open-open.com/show/6f67f5369aa536834235a823face898d.png"> 以上操作完成后即会在captures目录生成 com.zjw.appmethodorder_2017.03.25_21.41.trace 文件，android studio会默认打开一个可视化窗口</p> <p><img src="https://simg.open-open.com/show/38e46335aa0ffcfba60137957c2f9619.png"></p> <p>然后双击右侧面板的 AppOutPutMethodOrder 任务 如下图 <img src="https://simg.open-open.com/show/6186f2d3132a68fe935fe17e8aff5ec6.png"></p> <p>这一步完成就将在 captures 目录生成 base_order.txt 文件，该文件包含所有函数执行顺序</p> <p>等待任务执行完成，再执行 AppFilterMethodOrder 任务 如下图窗口</p> <p><img src="https://simg.open-open.com/show/90af49f6b5f86749f98ef9f2b5e17c5e.png"> 该任务目的就是过滤其他非相关包名，留下自己包名的函数，任务执行完成将在 captures 目录生成 order.txt 文件 如下图： <img src="https://simg.open-open.com/show/6413019633cd5ac36fe25fba4d97ee9f.png"> 接下来打开 order.txt 文件就是上文效果中的那样啦。</p> <h2>4.关于扩展和改造</h2> <p><img src="https://simg.open-open.com/show/6c165a00a3f7d1e3752e47185b2251ca.png"> 这里稍作修改即可。注意 AppOutPutMethodOrder 任务一直是以最新时间生成的.trace文件作为生成base_order.txt基准的。</p> <p> </p> <p>项目主页：<a href="http://www.open-open.com/lib/view/home/1490751205225">http://www.open-open.com/lib/view/home/1490751205225</a></p> <p></p>