Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • TTool TTool
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 62
    • Issues 62
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • mbe-tools
  • TToolTTool
  • Merge requests
  • !364

Fix memory leak problem

  • Review changes

  • Download
  • Email patches
  • Plain diff
Closed Le Van Truong requested to merge revert-883077ef into master Nov 20, 2020
  • Overview 0
  • Commits 1
  • Pipelines 0
  • Changes 2

I have just fixed the memory leak problems showed by valgrind. Here are some notes:

  • To run valgrind efficiently we need to compile the simulator with "-Wall -ggdb3" option.
  • The memory leak appears due to some variables are not to be freed. I have already freed it.
  • Now the simulator can run normally without memory leak but valgrind also shows the issues about "Conditional jump or move depends on uninitialised value(s)". This issue happens because there are a lot of variables defined in header file without initial value and they will be assigned value on cpp file.
  • Also valgrind has an option "--track-origins=yes" to track down where is "Conditional jump or move depends on uninitialised value(s)" occurs. I ran it and got no error, so I guess with the track down option valgrind will know where the variable is assigned value. This is common issue and it is not a memory leak issue.
Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: revert-883077ef