What steps will reproduce the problem?
1. Run bedtobam with a genome that is not a genome file
2. bedToBam -i foo.bed -g ../ > foo (this works)
3. samtools view foo -segfaults with no warning
What is the expected output? What do you see instead?
bedToBam should fail on bad input.
What version of the product are you using? On what operating system?
bedToBam (v2.16.2)
Original issue reported on code.google.com by gabriel....@gmail.com on 17 Aug 2012 at 6:35
Original issue reported on code.google.com by
gabriel....@gmail.com
on 17 Aug 2012 at 6:35