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
  • #193

Closed
Open
Opened Jun 08, 2016 by Shane Snyder@ssnyder
  • Report abuse
  • New issue
Report abuse New issue

make logutils API allocate records for caller

Currently, darshan logutils API expects an input buffer to be passed in to store module records it reads from the log file. The problem is that the caller might not always know how big the record it is about to extract is, particularly in cases where a module's records are variable-length (in which case one would need to sift through the data to determine the record size).

It would probably be better to just have the logutils API malloc memory for the current buffer it is extracting rather than relying on the caller to ensure there is enough space. This buffer can then be returned to the user where it will eventually need to be freed up.

Assignee
Assign to
3.1.0
Milestone
3.1.0
Assign milestone
Time tracking
None
Due date
None
1
Labels
enhancement
Assign labels
  • View project labels
Reference: darshan/darshan#193