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
After working with MP-SPDZ, I noticed that it has a lack of debugger tools for tracing the execution of a program, from compilation to execution. In order to be effective with any such library, developers need a way to debug their MPC programs.
At a minimum, our debugger should allow for
: Debugging compilation by creating an assembly output along with some important statistics
: Debugging execution on 1 or more MPC nodes and outputs their local view of what they're executing.
The text was updated successfully, but these errors were encountered:
Do you already have an idea of how to implement such a debugging functionality? Will it e.g. just be struct which can be attached to a VM or node, which offers some fine-grained logging functionality?
Yes, that's what I'm thinking. We can have a struct for both the VM and compiler since the information you'd want to see for both are different enough.
After working with MP-SPDZ, I noticed that it has a lack of debugger tools for tracing the execution of a program, from compilation to execution. In order to be effective with any such library, developers need a way to debug their MPC programs.
At a minimum, our debugger should allow for
The text was updated successfully, but these errors were encountered: