Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in
D
darshan
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 72
    • Issues 72
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 5
    • Merge Requests 5
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • darshan
  • darshan
  • Issues
  • #148

Closed
Open
Opened Sep 24, 2015 by Shane Snyder@ssnyder
  • Report abuse
  • New issue
Report abuse New issue

incorrect reporting of bytes read and written by HMMER application

See http://hmmer.janelia.org/. Problem reported by Chris Daley. Example execution reads gigabytes of data and writes 19 MiB of data, but Darshan reports 8 bytes read and roughly 1 MiB written. Application is using fread and fwrite for I/O, and everything shows up as expected in strace as read and write operations.

This indicates that there may be a bug in how Darshan records the sizes of fread and fwrite operations.

Removing from 2.2.9 milestone for now, but we should still try to produce a prototype to test with hmmer.

Assignee
Assign to
3.1.0
Milestone
3.1.0
Assign milestone
Time tracking
None
Due date
None
2
Labels
defect wrapper libraries
Assign labels
  • View project labels
Reference: darshan/darshan#148