Skip to content

frequent signal 11 / sigsegv #19

@ptrebert

Description

@ptrebert

Hi,
I have executed VerityMap on a number of haploid chromosomes w/o problems, but for the majority, then run fails with a segfault like this

[...]
00:00:38 0.72022-06-28 12:58:44 VerityMap started

*********************************
Read mapping started...
MAPPER_BIN exists
[...Python traceback omitted...]
subprocess.CalledProcessError: Command 
'['[ ...cut... ]/veritymap/build/bin/veritymap', '--target', 'output/subset_wg/20_extract_contigs/NA20509.HIFIRW.ONTUL.na.chrY.fasta',
 '--queries', 'output/subset_wg/45_extract_reads/NA20509.HIFIRW_aln-to_HIFIRW.ONTUL.na.chrY.reads.fasta.gz', 
'-o', '[ ...cut... ]/output/eval/assm_errors/NA20509.HIFIRW.ONTUL.na.chrY.HIFIRW/veritymap', 
'-t', '6', '--config', 'hifi']' died with <Signals.SIGSEGV: 11>.

I get the segfault for both HiFi and ONT reads. I have the info from other users that the mapper sometimes crashes but has already produced all necessary output. If that is the case here as well, can you briefly state which output file(s) are required to move on with the run:

alignments.sam
chains.tsv
kmer_indexes.tsv
norarekmers.bed

All of the above? In that case, I would modify the script to check for the existence of these files and ignore the error in that case.

Best,
Peter

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions