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.

Sign up for GitHub

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

Jump to bottom

Valgrind is not catching libpulp.so memory leaks #122

Open
giulianobelinassi opened this issue Apr 20, 2022 · 2 comments
Open

Valgrind is not catching libpulp.so memory leaks #122

giulianobelinassi opened this issue Apr 20, 2022 · 2 comments
Labels
bug Something isn't working

Comments

@giulianobelinassi
Copy link
Collaborator

There was a memory leak when handling ulp_metadata on libpulp.so which were not caught by valgrind. Probably the shell valgrind hack is not working as intended.
@giulianobelinassi giulianobelinassi added the bug Something isn't working label Apr 20, 2022
@giulianobelinassi
Copy link
Collaborator Author

Valgrind testing has been disabled in 9686d50

@giulianobelinassi
Copy link
Collaborator Author

Partial valgrind support was added in 7002e0a. To test patches with this, load the program with valgrind-gdb and call the interface functions to livepatch the function. Note that valgrind has to be started with self-modifying code support.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@giulianobelinassi