Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • 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 334
    • Issues 334
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 14
    • Merge requests 14
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Infrastructure Registry
  • External wiki
    • External wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • sac-group
  • sac2csac2c
  • Issues
  • #1025

Closed
Open
Created Mar 10, 2012 by Bep Rinto@broGuest

heap manager fails under valgrind and error reports are uninformative

Bugzilla Link 932
Created on Mar 10, 2012 10:36
Version 1.00beta
OS Linux
Architecture PC

Extended Description

When testing SAC programs with valgrind I get the following error message:
*** SAC runtime error
*** SAC heap manager failed to obtain 2097152 Bytes of memory from operating system !
The problems are that this message is unhelpful for the developer:
It doesn't report which operating system's function returned an error
and it doesn't report the errno or the error message using strerror(errno)
or the printf %m.
Also, could SAC be made to work under valgrind? 
This is a great debugging aid for developers,
which helps in making SAC and SAC programs more reliable.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking