- changed status to resolved
Segfault when indexing with high k
Issue #27
resolved
Here’s an example
ngs85out/test/nscat via C base ❯ kma index -k 40 -i nscat.fna -o nscat
# Indexing databases.
# Updating DBs
# Reading inputfile: nscat.fna
zsh: segmentation fault kma index -k 40 -i nscat.fna -o nscat
I don’t know if there are any reason it segfaults when k > 31 - perhaps the kmers are stored in signed 64 bit integers. Anyway, an error message would be much appreciated instead of a segfault :)
Comments (2)
-
-
I forgot to add it, thanks for the heads up. An error message has been added.
- Log in to comment
Updated VCF and fixed Issue
#27→ <<cset 9bc99b491a8b>>