I try to run a simple test with valgrind but it seems that valgrind can’t even start because of some memory limitation issue.
valgrind --leak-check=full --track-origins=yes echo 'test'
==26260== Valgrind's memory management: out of memory: ==26260== initialiseSector(TC)'s request for 27597024 bytes failed. ==26260== 143327232 bytes have already been allocated. ==26260== Valgrind cannot continue. Sorry.
490MB of my total RAM is consumed so I would guess that is not the reason behind this since valgrind is such a small tool. Also I run the test inside a docker container if that matters.
Any idea on how to solve?
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.
Click below to sign up and get $200 of credit to try our products over 60 days!