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

Run valgrind on Lind #329

Open
rennergade opened this issue Oct 19, 2023 · 1 comment
Open

Run valgrind on Lind #329

rennergade opened this issue Oct 19, 2023 · 1 comment
Assignees
Labels
good first issue Good for newcomers

Comments

@rennergade
Copy link
Contributor

We'd like to run vagrind on Lind to check for any memory leaks. Let's try to do this.

One issue is that our fork memory copy relies on mremap() which isn't allowed with valgrind. We can create and option to fallback to a straight memcpy the memory regions between cages on fork instead of the current setup and just enable that version when running valgrind.

@rennergade
Copy link
Contributor Author

This is probably a good issue for @Yaxuan-w to work on once she gets the initial SGX traces, since it would also make fork "no kernel"

@rennergade rennergade added the good first issue Good for newcomers label Jan 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

4 participants