Linked by Thom Holwerda on Tue 12th Oct 2010 21:52 UTC
Thread beginning with comment 444982
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[8]: Why all the fuss about Java?
by Neolander on Thu 14th Oct 2010 06:15
in reply to "RE[7]: Why all the fuss about Java?"
Valgrind is cool, even VERY cool but unfortunately it is not a solution to every memory problem. The reason for that is that valgrind works only for heap allocated memory and everything on stack or any static memory accesses won't be checked. Usually when I have very weird undebuggable memory problems I have to change my stack data to be dynamically allocated .. sometimes it reveals stuff .. but still it is a great inconvenience. Managed languages may have an advantage in this but still C/C++ rock.
Can you go in more details about those problems ? I'm curious.
Edited 2010-10-14 06:17 UTC




Member since:
2009-03-13
Ever heard of memory debugging tools like Valgrind ? Using them in testing is just as safe as using an interpreted language, but you don't need to perform slow checks *every time* a program is run.
Valgrind is cool, even VERY cool but unfortunately it is not a solution to every memory problem. The reason for that is that valgrind works only for heap allocated memory and everything on stack or any static memory accesses won't be checked. Usually when I have very weird undebuggable memory problems I have to change my stack data to be dynamically allocated .. sometimes it reveals stuff .. but still it is a great inconvenience. Managed languages may have an advantage in this but still C/C++ rock.