-
Notifications
You must be signed in to change notification settings - Fork 116
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
Invalid access in ssw_test #37
Comments
A binary built with clang 3.6.2 seems to produce different (imho better) alignments and no such problems. I wonder if it's related to compiler issues? GCC 4.9 also produces working binaries. Here's what the output looks like in this case:
|
After some debugging and hacking, I was able to produce a consistent build with the correct result after the following changes: satta@c341ce2 Apparently the result of The fact that optimization settings and inlining are involved makes me wonder if it's a boundary case in gcc being hit? |
Dear Satta, Thank you very much for your comments. I think this is very helpful. I was wondering would you mind to make a pull request with your changes, so that I can update the programs easily. Please let me know. Yours, Mengyao |
Hi Mengyao, done, please see #39. I'd like to point out that moving |
Dear Sascha, Thank you very much. I think this function won’t influence speed much. The most time consuming part is at the matrix calculation. Yours, Mengyao
|
OK, thanks for the merge; I will incorporate it as a patch into the Debian package unless you would be willing to tag a new version :) |
Dear Sascha, Thank you for making the Debian package. I think to tag a new version is better, so I made one here: I was wondering would you mind to test it before updating the Debian package? This one hasn’t been used much. Thank you so much. Please let me know, if you find any problem or have any comment. Yours, Mengyao
|
Sure, I can re-run the tests I did to trace the problem. However, it would be more natural if you could assign a version number in the tag that is greater than the last one ('v1.0'). The current one ('gcc') does not clearly indicate an order... that would be nice - thanks! |
Dear Sascha, Yes, you are right. I just changed it to v1.1. Many thanks, Mengyao
|
Looks good, the error seems to be gone now, and dependencies (like SPAdes) still pass their tests. I have updated the Debian package now, thanks for your work on this! |
Dear Sascha, Thank you. :-) Yours, Mengyao
|
Hi,
when running some test cases I noticed that sometimes the
ssw_test
tool prints binary characters in the BLAST like output; apparently as a result of accessing uninitialized memory.I just built it in a Debian stretch VM with a simple
make
(after adding-g
toCFLAGS
in the Makefile) using gcc version 5.4.0 20160609 (Debian 5.4.0-6). You can trigger the problematic behaviour using the test data included in the repo like this:Here's some Valgrind output that might be helpful:
It looks like the second sequence is exceeded when printing. I'm not sure whether this is just a formatting issue or something to do with the SW implementation itself; the SAM output also results in memory access issues according to Valgrind.
The text was updated successfully, but these errors were encountered: