Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • B Bio-DB-HTS
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 6
    • Issues 6
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Jira
    • Jira
  • Merge requests 0
    • Merge requests 0
  • Requirements
    • Requirements
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ensembl-gh-mirror
  • Bio-DB-HTS
  • Issues
  • #62

Closed
Open
Created Mar 14, 2018 by Marek Szuba@mks

htslib 1.3.1 (and older) non-compatible header_read for SAM

Created by: avullo

I've recently addressed #54 (closed), which involved seeking at the beginning of the buffer not only for BAM/CRAM but for SAM files as well, using a dedicated function call (hseek).

This works well for htslib >= 1.5, but generates segmentation faults for v1.3.1 and probably before.

I could see the hseek code in htslib has changed since then: there are some guards acting in special circumstances in the newer versions using hFILE attributes which are not defined in the older versions, but cannot say this is the cause for sure.

This is a problem which is preventing deployment of the upcoming v2.10 in the ensembl web environment, as they rely on htslib 1.3.1 (to support GRCh37 with samtools): the SAM file tests exit unexpectedly so they are deemed to fail. Obviously, this is affecting any installation which ties to htslib < 1.5.

Am I calling hseek correctly with htslib < 1.5.? https://github.com/Ensembl/Bio-DB-HTS/blob/master/lib/Bio/DB/HTS.xs#L496 I cannot see why not.

The current workaround has just the goal of avoiding seg faults and make the tests pass with htslib 1.3.1 and older. Unfortunately, this exposes #54 (closed) again in these cases.

Assignee
Assign to
Time tracking