-
Notifications
You must be signed in to change notification settings - Fork 20
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
segfault at end of bcalm (probably due to valgrind error) #2
Comments
OgraphBin is still in dev and should not be yet used. |
so we should use graph3? |
ograph3 has an issue as well:
To reproduce it: ../build/bcalm -in ~/bcalm-data/lambda-k16.fa -k 16 -abundance 1 https://transfer.sh/9h7XC/lambda-k16.fa (link will expire soon) |
I'll take care of it. |
okay thanks! |
I can't reproduce the error. |
Indeed, with this new version, I do not get a valgrind error during the execution anymore! The crash remains at the end of the execution, however it disappears when bcalm is compiled in debug mode. Valgrind output is not helpful without debug information.
Neither is gdb:
I'm on it. |
it was related to a call in initBinSeq, that I just commented out because we don't use binSeq at the moment. |
Problem is in ographBin:
The text was updated successfully, but these errors were encountered: