Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Think about Debugger tools #9

Open
2 tasks
Mikerah opened this issue Nov 21, 2021 · 2 comments
Open
2 tasks

Think about Debugger tools #9

Mikerah opened this issue Nov 21, 2021 · 2 comments

Comments

@Mikerah
Copy link
Contributor

Mikerah commented Nov 21, 2021

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.
@th4s
Copy link
Contributor

th4s commented Nov 22, 2021

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?

@Mikerah
Copy link
Contributor Author

Mikerah commented Nov 22, 2021

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.

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

No branches or pull requests

2 participants