[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ASZV9W97CBZTG6VGTYW9Z0":3,"skill-same:01M7ASZV9W97CBZTG6VGTYW9Z0":59},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7ASZV9W97CBZTG6VGTYW9Z0","re-tracing",null,"系统调用\u002F函数调用跟踪：strace\u002Fltrace\u002Fdtruss。 触发词：strace、跟踪系统调用、ltrace、API监控","dslsdzc\u002Frev-skills","dslsdzc","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F150430440?v=4","01M7ASEW5AKHWCFR1TXPAXQ237","DslsDZC","01M7ASEW5WJZ3GGBCCT12KHAQZ",243,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdslsdzc\u002Frev-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fre-tracing\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: re-tracing\ndescription: >\n  系统调用\u002F函数调用跟踪：strace\u002Fltrace\u002Fdtruss。\n  触发词：strace、跟踪系统调用、ltrace、API监控\ncapabilities: [tracing]\n---\n\n# 系统调用\u002F函数调用跟踪\n\n## 何时使用 \u002F 何时不用\n\n- 用：观察程序运行行为（文件\u002F网络\u002F进程操作）；记录系统调用与库调用序列作为证据；定位动态解析的 API（GetProcAddress\u002Fdlopen 之后）\n- 不用：只需内存内容（走 [[re-memdump]]）；只需静态逻辑（反编译技能）\n- 不用：Windows 目标用 APIMonitor\u002FProcMon（本技能 Linux\u002FmacOS 为主）\n\n## 工具准备\n\n参考 [[re-analyze\u002Fplatform-tips]] 最高原则——跟踪即动态执行，默认在沙箱内进行，网络隔离。\n\n### strace（Linux）\n\n- Debian\u002FUbuntu: `apt install strace`\n- Fedora\u002FRHEL: `dnf install strace`\n- Arch: `pacman -S strace`\n- WSL: Linux 包直接可用\n- 验证: `strace -V`\n- 常用选项：`-f` 跟子进程、`-o` 写文件、`-e trace=` 过滤、`-s 200` 放大字符串显示（默认 32 字节）、`-x` 非 ASCII 转十六进制、`-y`\u002F`-yy` 把 fd 解析为路径、`-c` 汇总统计、`-p` attach——速查与组合见 [[commands]]\n\n### ltrace（Linux 库调用）\n\n- Debian\u002FUbuntu: `apt install ltrace`\n- Fedora\u002FRHEL: `dnf install ltrace`\n- Arch: `pacman -S ltrace`\n- 验证: `ltrace -V`\n\n### dtruss（macOS，DTrace 版 strace）\n\n- macOS 自带（随 Xcode CLT）；需要 root 且部分 SIP 场景受限\n- 验证: `sudo dtruss -c ls \u002F 2>&1 | head` 输出去重调用统计\n\n### APIMonitor \u002F ProcMon（Windows）\n\n- APIMonitor: rohitab.com 下载 zip 解压即用\n- ProcMon: Microsoft Sysinternals —— `choco install sysinternals`（或官网下载）\n- 验证: 打开 APIMonitor\u002FProcMon 能列出并附加进程\n\n## 操作步骤\n\n1. **strace -f 全进程树跟踪**：\n   ```sh\n   strace -f -o trace.log .\u002Ftarget args\n   ```\n   `-f` 必须加：跟随 fork\u002Fvfork\u002Fclone 子进程——不加会漏掉全部子进程行为。\n   `-tt` 加微秒时间戳，`-T` 加每调用耗时（网络等待\u002F慢调用线索）；`-s 200` 放大字符串显示（默认 32 字节，路径\u002F参数看不全时必加）。\n   已运行的目标用 attach（看不到 attach 之前的调用）：\n   ```sh\n   sudo strace -f -p \u003Cpid> -o attach.log     # attach 需要与目标同权限\n   strace -f -c .\u002Ftarget                      # 退出时打印系统调用计数\u002F耗时汇总（热点定位）\n   ```\n\n2. **过滤（-e trace=...）**：\n   ```sh\n   strace -f -e trace=network,file .\u002Ftarget     # 只看网络与文件\n   strace -f -e trace=write,read .\u002Ftarget       # 只看读写\n   strace -f -e trace=execve,fork,clone .\u002Ftarget # 只看进程行为\n   strace -f -e trace=!futex .\u002Ftarget           # 排除噪声（futex 高频）\n   ```\n   过滤规则先白名单后黑名单，控制输出体积（见坑 2）。\n\n3. **ltrace 库调用**：\n   ```sh\n   ltrace -f -o lib.log .\u002Ftarget\n   ltrace -e malloc+free .\u002Ftarget        # 只跟踪指定库函数\n   ltrace -l \u002Fpath\u002Flibfoo.so .\u002Ftarget    # 跟踪 dlopen 动态加载的库\n   ltrace -f -S .\u002Ftarget                 # 库调用 + 系统调用一起跟踪\n   ltrace -f -c .\u002Ftarget                 # 退出时库调用汇总\n   ```\n   动态解析的 API（`dlsym` 拿到的函数）不会出现在静态 IAT 里，但会出现在 ltrace 输出中——与 [[re-imports]] 互补。\n\n4. **输出保存为证据**：\n   ```sh\n   strace -f -tt -o evidence\u002Ftrace-$(date +%s).log .\u002Ftarget\n   # 或\n   ltrace -f -o evidence\u002Flibcall.log .\u002Ftarget\n   ```\n   每条记录带 pid 与时间戳；分析完成后在笔记中引用文件路径与哈希（样本与日志各存 sha256，见 [[re-triage]]）。\n\n5. **Windows 用 APIMonitor\u002FProcMon**：\n   - APIMonitor: 运行（管理员）→ 选中目标进程 → 勾选要监控的 API 类（File\u002FNetwork\u002FRegistry\u002FProcess）→ 附加，观察调用参数与返回值\n   - ProcMon: 全系统级（文件\u002F注册表\u002F网络\u002F进程事件），先按进程过滤（Process Name 过滤目标名），再按 Operation 过滤\n   - 可疑点: 对注入类 API 连续调用序列（OpenProcess→VirtualAllocEx→WriteProcessMemory→CreateRemoteThread）即恶意行为证据\n\n## 指令级追踪\n\n比系统调用级更深一层——指令粒度执行流：\n\n- **QEMU 插件**：`-plugin` 加载指令级 trace 插件（insn 粒度、call\u002Fret 路径、guest 代码块事件）；用途——脱壳后真实路径还原、反混淆（静态混淆无法隐藏实际执行）\n- **Intel PT**：硬件 trace（`perf record -e intel_pt`）→ 解码（`perf script` 或第三方解析）→ 分支流还原；用途——无插桩开销的完整执行路径\n- **trace 分析**：热点（执行频次排序）、路径还原（调用链重建）、与 [[re-deobfuscate]] 衔接（按真实路径过滤死代码）\n- **输出**：指令级执行流摘要（供 [[re-analyze\u002Fanalysis-contract]] 证据存档）\n\n## 跨域联合\n\n- [[re-binary-core]]：工作流第 6 步（行为跟踪）\n- [[re-malware]]：恶意行为观察（回连\u002F持久化\u002F自启动）\n- [[re-cracking]]：监控校验\u002F注册相关的 API 调用参数\n- 与 [[re-imports]] 互补（动态解析 API）；发现反调试时转 [[re-anti-analysis]]\n- [[re-ebpf]]：BPF 观测\u002F跟踪取证还原——strace 覆盖不到的 skb\u002F内核路径由 BPF 观测互补\n\n## 常见坑与陷阱\n\n- **不加 -f 漏子进程**：目标 fork 后父进程退出\u002Fexec，未跟踪的子进程行为全部丢失——`-f` 是标配\n- **输出巨大**：不过滤时大程序日志可达 GB 级拖垮磁盘——先 `-e trace=` 白名单，必要时 `-o` 写文件而非终端\n- **反调试样本检测 trace 环境**：`ptrace` 状态检测\u002F`LD_PRELOAD` 痕迹暴露 strace\u002Fltrace——与 [[re-anti-analysis]] 的反调试绕过组合使用\n- ltrace 默认只跟踪 PLT 层调用——`dlopen` 后加载的库函数要加 `-l` 显式指定\n- 命令族速查与操作序列见 [[commands]]；工具特有坑与版本差异见 [[gotchas]]\n","# 系统调用\u002F函数调用跟踪\n\n## 何时使用 \u002F 何时不用\n\n- 用：观察程序运行行为（文件\u002F网络\u002F进程操作）；记录系统调用与库调用序列作为证据；定位动态解析的 API（GetProcAddress\u002Fdlopen 之后）\n- 不用：只需内存内容（走 [[re-memdump]]）；只需静态逻辑（反编译技能）\n- 不用：Windows 目标用 APIMonitor\u002FProcMon（本技能 Linux\u002FmacOS 为主）\n\n## 工具准备\n\n参考 [[re-analyze\u002Fplatform-tips]] 最高原则——跟踪即动态执行，默认在沙箱内进行，网络隔离。\n\n### strace（Linux）\n\n- Debian\u002FUbuntu: `apt install strace`\n- Fedora\u002FRHEL: `dnf install strace`\n- Arch: `pacman -S strace`\n- WSL: Linux 包直接可用\n- 验证: `strace -V`\n- 常用选项：`-f` 跟子进程、`-o` 写文件、`-e trace=` 过滤、`-s 200` 放大字符串显示（默认 32 字节）、`-x` 非 ASCII 转十六进制、`-y`\u002F`-yy` 把 fd 解析为路径、`-c` 汇总统计、`-p` attach——速查与组合见 [[commands]]\n\n### ltrace（Linux 库调用）\n\n- Debian\u002FUbuntu: `apt install ltrace`\n- Fedora\u002FRHEL: `dnf install ltrace`\n- Arch: `pacman -S ltrace`\n- 验证: `ltrace -V`\n\n### dtruss（macOS，DTrace 版 strace）\n\n- macOS 自带（随 Xcode CLT）；需要 root 且部分 SIP 场景受限\n- 验证: `sudo dtruss -c ls \u002F 2>&1 | head` 输出去重调用统计\n\n### APIMonitor \u002F ProcMon（Windows）\n\n- APIMonitor: rohitab.com 下载 zip 解压即用\n- ProcMon: Microsoft Sysinternals —— `choco install sysinternals`（或官网下载）\n- 验证: 打开 APIMonitor\u002FProcMon 能列出并附加进程\n\n## 操作步骤\n\n1. **strace -f 全进程树跟踪**：\n   ```sh\n   strace -f -o trace.log .\u002Ftarget args\n   ```\n   `-f` 必须加：跟随 fork\u002Fvfork\u002Fclone 子进程——不加会漏掉全部子进程行为。\n   `-tt` 加微秒时间戳，`-T` 加每调用耗时（网络等待\u002F慢调用线索）；`-s 200` 放大字符串显示（默认 32 字节，路径\u002F参数看不全时必加）。\n   已运行的目标用 attach（看不到 attach 之前的调用）：\n   ```sh\n   sudo strace -f -p \u003Cpid> -o attach.log     # attach 需要与目标同权限\n   strace -f -c .\u002Ftarget                      # 退出时打印系统调用计数\u002F耗时汇总（热点定位）\n   ```\n\n2. **过滤（-e trace=...）**：\n   ```sh\n   strace -f -e trace=network,file .\u002Ftarget     # 只看网络与文件\n   strace -f -e trace=write,read .\u002Ftarget       # 只看读写\n   strace -f -e trace=execve,fork,clone .\u002Ftarget # 只看进程行为\n   strace -f -e trace=!futex .\u002Ftarget           # 排除噪声（futex 高频）\n   ```\n   过滤规则先白名单后黑名单，控制输出体积（见坑 2）。\n\n3. **ltrace 库调用**：\n   ```sh\n   ltrace -f -o lib.log .\u002Ftarget\n   ltrace -e malloc+free .\u002Ftarget        # 只跟踪指定库函数\n   ltrace -l \u002Fpath\u002Flibfoo.so .\u002Ftarget    # 跟踪 dlopen 动态加载的库\n   ltrace -f -S .\u002Ftarget                 # 库调用 + 系统调用一起跟踪\n   ltrace -f -c .\u002Ftarget                 # 退出时库调用汇总\n   ```\n   动态解析的 API（`dlsym` 拿到的函数）不会出现在静态 IAT 里，但会出现在 ltrace 输出中——与 [[re-imports]] 互补。\n\n4. **输出保存为证据**：\n   ```sh\n   strace -f -tt -o evidence\u002Ftrace-$(date +%s).log .\u002Ftarget\n   # 或\n   ltrace -f -o evidence\u002Flibcall.log .\u002Ftarget\n   ```\n   每条记录带 pid 与时间戳；分析完成后在笔记中引用文件路径与哈希（样本与日志各存 sha256，见 [[re-triage]]）。\n\n5. **Windows 用 APIMonitor\u002FProcMon**：\n   - APIMonitor: 运行（管理员）→ 选中目标进程 → 勾选要监控的 API 类（File\u002FNetwork\u002FRegistry\u002FProcess）→ 附加，观察调用参数与返回值\n   - ProcMon: 全系统级（文件\u002F注册表\u002F网络\u002F进程事件），先按进程过滤（Process Name 过滤目标名），再按 Operation 过滤\n   - 可疑点: 对注入类 API 连续调用序列（OpenProcess→VirtualAllocEx→WriteProcessMemory→CreateRemoteThread）即恶意行为证据\n\n## 指令级追踪\n\n比系统调用级更深一层——指令粒度执行流：\n\n- **QEMU 插件**：`-plugin` 加载指令级 trace 插件（insn 粒度、call\u002Fret 路径、guest 代码块事件）；用途——脱壳后真实路径还原、反混淆（静态混淆无法隐藏实际执行）\n- **Intel PT**：硬件 trace（`perf record -e intel_pt`）→ 解码（`perf script` 或第三方解析）→ 分支流还原；用途——无插桩开销的完整执行路径\n- **trace 分析**：热点（执行频次排序）、路径还原（调用链重建）、与 [[re-deobfuscate]] 衔接（按真实路径过滤死代码）\n- **输出**：指令级执行流摘要（供 [[re-analyze\u002Fanalysis-contract]] 证据存档）\n\n## 跨域联合\n\n- [[re-binary-core]]：工作流第 6 步（行为跟踪）\n- [[re-malware]]：恶意行为观察（回连\u002F持久化\u002F自启动）\n- [[re-cracking]]：监控校验\u002F注册相关的 API 调用参数\n- 与 [[re-imports]] 互补（动态解析 API）；发现反调试时转 [[re-anti-analysis]]\n- [[re-ebpf]]：BPF 观测\u002F跟踪取证还原——strace 覆盖不到的 skb\u002F内核路径由 BPF 观测互补\n\n## 常见坑与陷阱\n\n- **不加 -f 漏子进程**：目标 fork 后父进程退出\u002Fexec，未跟踪的子进程行为全部丢失——`-f` 是标配\n- **输出巨大**：不过滤时大程序日志可达 GB 级拖垮磁盘——先 `-e trace=` 白名单，必要时 `-o` 写文件而非终端\n- **反调试样本检测 trace 环境**：`ptrace` 状态检测\u002F`LD_PRELOAD` 痕迹暴露 strace\u002Fltrace——与 [[re-anti-analysis]] 的反调试绕过组合使用\n- ltrace 默认只跟踪 PLT 层调用——`dlopen` 后加载的库函数要加 `-l` 显式指定\n- 命令族速查与操作序列见 [[commands]]；工具特有坑与版本差异见 [[gotchas]]\n",{"name":5,"description":24,"capabilities":25},"系统调用\u002F函数调用跟踪：strace\u002Fltrace\u002Fdtruss。 触发词：strace、跟踪系统调用、ltrace、API监控\n",[26],"tracing","main","1977504515d3f5fa8889da43974feb7a0f4eaab9",".claude\u002Fskills\u002Fre-tracing",43,"https:\u002F\u002Fgithub.com\u002Fdslsdzc\u002Frev-skills","https:\u002F\u002Fgithub.com\u002Fdslsdzc","Building systems from scratch","2026-10-12 04:15:49",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add dslsdzc\u002Frev-skills --skill re-tracing",{"tool":41,"command":42},"bunx","bunx skills add dslsdzc\u002Frev-skills --skill re-tracing",{"tool":44,"command":45},"pnpm","pnpm dlx skills add dslsdzc\u002Frev-skills --skill re-tracing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdslsdzc\u002Frev-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fre-tracing\u002FSKILL.md",true,[49,55],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fcommands.md","REFERENCE","参考文档",4599,"https:\u002F\u002Fgithub.com\u002Fdslsdzc\u002Frev-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fre-tracing\u002Freferences\u002Fcommands.md",{"path":56,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fgotchas.md",3561,"https:\u002F\u002Fgithub.com\u002Fdslsdzc\u002Frev-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fre-tracing\u002Freferences\u002Fgotchas.md",[60,67,73,80,87,94],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7AT3SFGN6KTM2DBN8TCNC4K","no-tools","缺工具准备章节。missing tools section.","https:\u002F\u002Fgithub.com\u002Fdslsdzc\u002Frev-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fno-tools\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7AT3PY0QVB4A4WGAZHY43WP","good-skill","https:\u002F\u002Fgithub.com\u002Fdslsdzc\u002Frev-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fgood-skill\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7AT3NJ1PG8DR115AMJC1Q1C","gateway-skill","网关型技能，无工具准备章节。gateway skill.","https:\u002F\u002Fgithub.com\u002Fdslsdzc\u002Frev-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fgateway-skill\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7AT3KCJGZV60PKJX244V8Z4","broken-link","含死链接与合法 references 链接。broken link.","https:\u002F\u002Fgithub.com\u002Fdslsdzc\u002Frev-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fbroken-link\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7AT3HMVTA2MR66A5FMATVFQ","wrong-name","名字与目录不符。name mismatch.","https:\u002F\u002Fgithub.com\u002Fdslsdzc\u002Frev-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fbad-name\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7AT3F4K5ES6N62092Y8TRNG","bad-frontmatter","https:\u002F\u002Fgithub.com\u002Fdslsdzc\u002Frev-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fbad-frontmatter\u002FSKILL.md",[],[]]