Export p-code and intermediate steps in "Debug Function Decompilation"

[H-A-M-G-E-R]

from

exports an XML containging debug info
but doesn't export p-code and intermediate steps

[msm-code]

You can load that file into decomp_dbg and get both p-code and intermediate steps.

[LukeSerne]

I built DecompVis to solve exactly this problem - I wanted to understand what transformation each rule made, and why the rule I was writing at the time did not get applied. The output of print raw can be difficult to understand, and seeing what a specific rule does exactly is also quite difficult using just decomp_dbg.

DecompVis uses decomp_dbg and the trace address and trace break 0 commands to set "breakpoints" after almost every rule application (see the get_decompile_data function). Additionally, print raw is used at each "breakpoint" to get the current state of the p-code, since the running diffs can be incomplete (see #4963).

Unfortunately, the raw pcode printed by print raw can be ambiguous. For example, print raw's output makes no distinction between INT_LESS (unsigned integer less-than) and INT_SLESS (signed integer less-than). I created an issue (#4951) and PR (#5063) for this, but there doesn't seem to be any progress in getting this fixed.