Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • sac2c sac2c
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 402
    • Issues 402
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 13
    • Merge requests 13
  • Deployments
    • Deployments
    • Releases
  • Wiki
    • Wiki
  • External wiki
    • External wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • sac-group
  • sac2csac2c
  • Issues
  • #2171
Closed
Open
Created Dec 11, 2009 by Daniel Rolls@dsrGuest

Potential memory leak in StringArray

Bugzilla Link 616
Created on Dec 11, 2009 00:07
Version svn
OS All
Architecture PC
Attachments testStringArray3.sac

Extended Description

Created an attachment (id=619)
testcase (SaC source)
The attached test case when run with
  sac2c -check ctb testStringArray3.sac && a.out
triggers a segfault in the first call to free in
modules/structures/src/StringArray/sel.c. Carl and I fixed this for now by
commenting out this line but don't know how this works. We may have even
inadvertently created a memory leak. To reproduce the problem first uncomment
the call to SAC_ND_DEC_RC_FREE and run the test case as described above.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking