-
Notifications
You must be signed in to change notification settings - Fork 405
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
A bug detected by valgrind-3.16.1 in minimap2-2.20_x64-linux ? #752
Labels
Comments
Actually in both cases, the conditional jumps from uninitialized values would lead to a deadend and the results are not used downstream. They are both harmless. I still fixed these anyway. Thanks for the report. |
I have got a similar bug report. I will look into this later. Thanks. |
It is a bug caused by that commit. Please try the latest github HEAD. I believe it has been fixed. |
Luke20000429
pushed a commit
to Minimap2onGPU/mm2-gb
that referenced
this issue
Jun 7, 2022
This one is harmless.
Luke20000429
pushed a commit
to Minimap2onGPU/mm2-gb
that referenced
this issue
Jun 7, 2022
Resolves lh3#752 (again)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi heng,
I wonder if this is a bug? I have attached the input files:
map.fa.gz
ref.fa.gz
Here is the CMD and log:
The text was updated successfully, but these errors were encountered: