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

segfault with empty query file in blastn mode #102

Closed
f-heeger opened this issue Jun 22, 2017 · 5 comments
Closed

segfault with empty query file in blastn mode #102

f-heeger opened this issue Jun 22, 2017 · 5 comments
Assignees
Milestone

Comments

@f-heeger
Copy link

I get a segfault when I run blastn mode with a empty query file. In default mode I get a correct error message.

To reproduce (with attached input files):

lambda-1.9.2-Linux-x86_64_sse4/bin/lambda_indexer -d testd.fasta -p blastn
lambda-1.9.2-Linux-x86_64_sse4/bin/lambda -q >testq.fasta -i testd.fasta.lambda -p blastn

I get this output:

LAMBDA - the Local Aligner for Massive Biological DatA
======================================================
Version 1.9.2

Loading Subj Sequences... done.
Loading Subj Ids... done.
Loading Database Index... done.
Loading Query Sequences and Ids... generating reverse complements...Segmentation fault (core >dumped)

test.zip

@h-2
Copy link
Member

h-2 commented Jun 23, 2017

This is actually a SeqAn bug, but I will provide a workaround in Lambda!

@h-2
Copy link
Member

h-2 commented Jun 23, 2017

@f-heeger the fix is quite easy, do you want to do a pull request? 😄

@h-2 h-2 added this to the 1.9.3 milestone Jun 23, 2017
@f-heeger
Copy link
Author

Absolutely not.

@h-2
Copy link
Member

h-2 commented Jun 27, 2017

@f-heeger Look at it, it's a really tiny diff :)
Can you verify that it fixes your problem? [note that indexes from lambda-next branch are incompatible to 1.9.2's]

@f-heeger
Copy link
Author

Yes it's fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants