Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • mbdyn mbdyn
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 22
    • Issues 22
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • DAER
  • mbdynmbdyn
  • Issues
  • #36

Closed
Open
Created Mar 15, 2020 by Andrea Zanoni@10260632Maintainer

RTSolver: RTSteps not initialized

The counter RTSteps in RTSolver is never actually initialized in the class constructor. This can lead to RT solvers not getting the initial reference time on systems in which RTSteps is not automatically initialized to 0: for example, in RTPOSIXSolver::Wait(), the call to clock_gettime() is skipped.

The fix is trivial and already written in the branch 'rtposixsolver_fix`, which I'm about to merge.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking