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 the GKL codebase #107

Closed
droazen opened this issue Apr 28, 2020 · 2 comments
Closed

Run valgrind on the GKL codebase #107

droazen opened this issue Apr 28, 2020 · 2 comments
Assignees

Comments

@droazen
Copy link

droazen commented Apr 28, 2020

Maybe it can catch some of these pointer safety issues reported in other tickets...

@Kmannth
Copy link
Contributor

Kmannth commented Sep 23, 2020

@droazen Do happen to have BKMs for Valgrind and GATK? We have spent some time trying to get symbol resoltion for GATK and GKL with valgrind but so far not much sucess.

@Kmannth
Copy link
Contributor

Kmannth commented Feb 3, 2021

Summary: The Valgrind and Java do not work well. #91 was updated to run with Master was was last tested Jan 2021. We will work to run this test as part of our regular release process.

With the latest code base and the limtied unit test cases no errors were found.

@Kmannth Kmannth closed this as completed Feb 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants