bytedance / bytedance/btrace

make project时 部分显示[MethodTracer] Failed

Open
#121 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
C++
Stars
2.5k
Forks
335
PR merge metrics
No merged PRs in 30d

Description

1. PC 环境:mac ;系统版本 14.3;JDK 版本 8;Python 版本 3.11.7;执行命令 java -jar rhea-trace-shell.jar -a com.storemonitor.app -t 10 -o output.pb -r rhea.all sched -fullClassName;
2. 手机环境:一加8t、Android 13;app 正常启动;无崩溃;
3. APK文件:64 位;assets 目录不包含 methodMapping.txt 文件;dex 中是否包含 Trace.i、Trace.o 的插桩代码,方式[参考这里](https://developer.android.com/studio/debug/apk-analyzer#show_bytecode_find_usages_and_generate_keep_rule);
4. 编译环境:AGP 4.1.3、Java 8。

![image](https://github.com/bytedance/btrace/assets/33115963/0849fb0d-47ab-47af-8685-838d7d1d3846)
想问下make project过程报这种错但是build成功了,会有什么影响么?我是不是需要单独把这些三方库配置成不插桩?

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the `java -jar rhea-trace-shell.jar` command with the listed macOS, JDK, Python, Android, APK, and AGP details, then inspect the build output and the APK with Android Studio’s APK Analyzer. Determine whether the `[MethodTracer] Failed` messages affect tracing output or only appear during a successful build, and document whether third-party libraries need separate configuration.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, java, python
Domain
build-system, mobile-dev, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.