[x] Searched for existing issues and pull requests.
Description
Description of the issue.
Am encountering a Segmentation fault (core dumped) error when running C benchmarks of mathematical functions.
Questions
Any questions for reviewers?
No.
Other
Any other information relevant to this issue? This may include screenshots, references, stack traces, sample output, and/or implementation notes.
The issue seems to be due to the benchmarks overflowing the default maximum stack size of 8 MB.
Increasing the stack size via e.g. ulimit -s 32767 causes the benchmarks to run properly.
We might want to rethink whether to allocate memory with malloc.
Reproduction
What steps are required to reproduce the unexpected output?
What environments are affected (e.g., Node v0.4.x, Chrome, IE 11)? If Node.js, include the npm version, operating system, and any other potentially relevant platform information.
Checklist
Description
Am encountering a
Segmentation fault (core dumped)
error when running C benchmarks of mathematical functions.Questions
No.
Other
The issue seems to be due to the benchmarks overflowing the default maximum stack size of 8 MB. Increasing the stack size via e.g.
ulimit -s 32767
causes the benchmarks to run properly.We might want to rethink whether to allocate memory with
malloc
.Reproduction
In order to reproduce this bug, do the following:
stdlib
directory, runExpected Results
The benchmarks should run without issues.
Actual Results
The following are the actual results:
Environments
The following environments are affected: