Skip to content

feat: add debug-output feature for routing MASM debug output to a custom sink#2302

Draft
juan518munoz wants to merge 1 commit into
nextfrom
jmunoz-expose-debugger
Draft

feat: add debug-output feature for routing MASM debug output to a custom sink#2302
juan518munoz wants to merge 1 commit into
nextfrom
jmunoz-expose-debugger

Conversation

@juan518munoz

Copy link
Copy Markdown
Collaborator

No description provided.

…tom sink

Add the `debug-output` feature and two client methods, `execute_program_with_debugger` and `execute_transaction_with_debugger`, which run a script or transaction with its MASM debug.* / trace.* output routed to a caller-supplied `fmt::Write` sink instead of stdout (a no-op on wasm32-unknown-unknown). This lets consumers such as @miden-sdk/miden-sdk surface debug output in the browser console.

The feature is no_std-compatible, unlike `dap`. `debug-output` is added to the CI test feature set so the unit test runs upstream.
@juan518munoz
juan518munoz force-pushed the jmunoz-expose-debugger branch from 53fc096 to de8f5d4 Compare July 3, 2026 14:36

@igamigo igamigo left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This LGTM, but how is this going to be consumed in the Web SDK? Will it always execute with the debug executor?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants