Skip to content
Snippets Groups Projects
Select Git revision
  • 55d7bef552312801dca6421ad9b527d4ba1b33d7
  • develop default protected
  • master
  • hts_opt_block_size
  • bz2-lzma-pkgconfig
  • exp/raw-index
  • cram_split_tags
  • configure
  • feature/contig_comma
  • parser-flags
  • irods_update
  • cigar-P-bis
  • cram_digests
  • CSIv2
  • ftype
  • lite
  • norm-indels
  • 1.8
  • 1.7
  • 1.6
  • 1.5
  • 1.4.1
  • 1.4
  • 1.3.2
  • 1.3.1
  • 1.3
  • 1.2.1
  • 1.2
  • 1.1
  • 1.0
  • 0.2.0-rc12
  • 0.2.0-rc11
  • 0.2.0-rc10
  • 0.2.0-rc9
  • 0.2.0-rc8
  • 0.2.0-rc7
  • 0.2.0-rc6
37 results

htslib

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Rob Davies authored
    Change kputsn() and kputsn_() to take size_t instead ot int to
    fix possible integer overflow in kputs.  They are both static inline
    so we can do this without breaking the ABI.  Guards on integer
    wrap-around should catch attempts to add over- or negatively- long
    strings.
    
    Possible buffer overflow in cram_populate_ref().
    
    Possible use of uninitialised value in bcf_sr_regions_next().  In
    that function it is possible that `from` and `to` may not be set if
    either `ifrom` or `ito` is negative as that could cause
    _regions_parse_line() to skip setting them.
    
    String truncation warning in bam_hdr_write() when compiled with
    no optimisation.  There was no need to copy the string anyway,
    it can just be written out directly.
    
    Not caught by gcc: Possible overflow in expand_cache_path().
    
    Silence false positive uninitialised value warning in cram_encode.c
    process_one_read() when using optimisation -Og or -Os.  gcc fails
    to spot that `new = 1` prevents `k` from being used if not set.
    55d7bef5
    History
    Name Last commit Last update