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

Segmentation Fault - file size? #12

Open
VBHerrenC opened this issue Jun 10, 2024 · 3 comments
Open

Segmentation Fault - file size? #12

VBHerrenC opened this issue Jun 10, 2024 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@VBHerrenC
Copy link

Hello,

In my attempts to use ViralConsensus on the command line, I'm having trouble with certain reference fastas. When I provide a reference of 4153 nt, a consensus fasta is outputted properly. When I decrease the size of the reference to something less than 4150 nt, it throws a segmentation fault. The same errors are repeated on the web version. Is it possible there is a minimum size for the reference sequence? Any help would be appreciated!

Thanks,
Calleigh

@niemasd
Copy link
Owner

niemasd commented Jun 10, 2024

Thank you for reaching out! I don't think there should be a minimum reference genome size, but there could be a bug somewhere (I've mainly tested on SARS-CoV-2). Do you happen to have an example reference genome + SAM/BAM file you would be able to share that triggers the segmentation fault? If you are able to provide one, I can use it to help me debug

@niemasd niemasd self-assigned this Jun 10, 2024
@niemasd niemasd added the bug Something isn't working label Jun 10, 2024
@VBHerrenC
Copy link
Author

VBHerrenC commented Jun 10, 2024

Hi,

Sorry, we figured it out! Turns out I was trying to provide a different reference than the one I had used to align the reads to. Thanks for the quick reply though!

@niemasd
Copy link
Owner

niemasd commented Jun 10, 2024

Thanks for double checking, and I'm glad to hear you figured it out! If possible, would you be able to share a small example dataset regardless? It would be good for me to add some error-checking to have it output a meaningful error message in this scenario instead of a generic "Segmentation Fault"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants