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 or corrupted output GFF when using -C coding only option on multiple NCBI genome assembly GFF files #108

Open
hermidalc opened this issue Nov 12, 2022 · 1 comment

Comments

@hermidalc
Copy link

hermidalc commented Nov 12, 2022

https://ftp.ncbi.nlm.nih.gov/genomes/all/GCA/000/843/825/GCA_000843825.1_ViralProj14424/GCA_000843825.1_ViralProj14424_genomic.gff.gz

This either segfaults or produces a corrupted output GFF file. I've run into other examples with NCBI genome assembly GFF files.

@hermidalc
Copy link
Author

hermidalc commented Nov 13, 2022

Might have to do with the fact this genome has five_prime_UTR and three_prime_UTR features, but gffread should be able to handle that and produce exon, CDS, and mRNA output features where the exon and mRNA ranges include the UTR regions and the CDS ranges do not.

@hermidalc hermidalc changed the title Segmentation fault or corrupted output GFF when using -C option with GCA_000843825.1 GFF file Segmentation fault or corrupted output GFF when using -C coding only option on multiple public NCBI genome assembly GFF files Nov 14, 2022
@hermidalc hermidalc changed the title Segmentation fault or corrupted output GFF when using -C coding only option on multiple public NCBI genome assembly GFF files Segmentation fault or corrupted output GFF when using -C coding only option on multiple NCBI genome assembly GFF files Nov 14, 2022
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

1 participant