Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • D darshan
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 72
    • Issues 72
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • darshan
  • darshan
  • Issues
  • #218
Closed
Open
Issue created Jan 20, 2017 by Glenn K. Lockwood@glockDeveloper

darshan_common_val_counter segfaults when common_val_count >= DARSHAN_COMMON_VAL_MAX_RUNTIME_COUNT

I have an application that segfaults inside darshan_common_val_counter() as a result of (apparently) *common_val_count reaching DARSHAN_COMMON_VAL_MAX_RUNTIME_COUNT. The found pointer is never defined, so by the time the following code is reached at the bottom of darshan_common_val_counter():

/* update common access counters as we go */
    DARSHAN_COMMON_VAL_COUNTER_INC(common_val_p, common_cnt_p,
        found->val, found->freq, 1);

found remains undefined and catastrophe results.

I'm not clear on how this condition of *common_val_count == DARSHAN_COMMON_VAL_MAX_RUNTIME_COUNT is reached, but found definitely is dereferenced before it is defined when it happens.

I can provide my application source if it would help. This bug happened using the 3.1.1 tag on both Cori/KNL and Cori/Haswell at NERSC.

Assignee
Assign to
Time tracking