You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should provide a way to map a Pc to its binary offset in the source module level for a better understanding of where the program crashed. Additionaly we need this mapping for future debugging support as DWARF information don't know Pc.
For now, all single "trappable" VM instruction corresponds to a single Wasm-level instruction (no unified instructions nor pseudo trappable VM instruction), so a Pc (at trappable instruction) -> BinaryOffset is injective.
We need to figure out how to build an address map function efficiently.
The text was updated successfully, but these errors were encountered:
We should provide a way to map a
Pc
to its binary offset in the source module level for a better understanding of where the program crashed. Additionaly we need this mapping for future debugging support as DWARF information don't knowPc
.For now, all single "trappable" VM instruction corresponds to a single Wasm-level instruction (no unified instructions nor pseudo trappable VM instruction), so a
Pc
(at trappable instruction) ->BinaryOffset
is injective.We need to figure out how to build an address map function efficiently.
The text was updated successfully, but these errors were encountered: