sac2c issueshttps://gitlab.sac-home.org/sac-group/sac2c/-/issues2017-11-19T20:17:38Zhttps://gitlab.sac-home.org/sac-group/sac2c/-/issues/1025heap manager fails under valgrind and error reports are uninformative2017-11-19T20:17:38ZBep Rintoheap manager fails under valgrind and error reports are uninformative| | |
| --- | --- |
| Bugzilla Link | [932](http://bugs.sac-home.org/show_bug.cgi?id=932) |
| Created on | Mar 10, 2012 10:36 |
| Version | 1.00beta |
| OS | Linux |
| Architecture | PC |
## Extended Description
<pre>When testing SAC...| | |
| --- | --- |
| Bugzilla Link | [932](http://bugs.sac-home.org/show_bug.cgi?id=932) |
| Created on | Mar 10, 2012 10:36 |
| Version | 1.00beta |
| OS | Linux |
| Architecture | PC |
## Extended Description
<pre>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.</pre>Clemens GrelckClemens Grelck