https://bugs.kde.org/show_bug.cgi?id=467087
--- Comment #4 from varun.yet...@cohere-technologies.com --- Sure. I compile with “-debug -O0 -g” flags. [yeturva@ran6 source]$ size ../bin/cpcc text data bss dec hex filename 87956828 383888 13069709208 13158049924 31047e884 ../bin/cpcc Regards, Varun From: Paul Floyd <bugzilla_nore...@kde.org> Date: Saturday, March 11, 2023 at 7:59 AM To: Varun Reddy Yeturu <varun.yet...@cohere-technologies.com> Subject: [valgrind] [Bug 467087] Unable to start Valgrind due to error (MMAP) https://bugs.kde.org/show_bug.cgi?id=467087 --- Comment #3 from Paul Floyd <pjfl...@wanadoo.fr> --- Centos is unlikely to be the problem - it is one of the best supported platforms. ICC is a lot less well supported - not sure if any Valgrind devs use it regularly. One quick thing that you can do is give use the output of 'size' on your executable. For instance paulf> size `which dolphin` text data bss dec hex filename 967740 114080 501 1082321 0x1083d1 /usr/local/bin/dolphin That's just some random KDE app, but it tells us how big the code is (text), global data (data) and static data (bss). -- You are receiving this mail because: You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
