Hey guys,
Was just wondering you guys had heard of any Memory managment tools for windoes. Like Valgrind for Unix platform.
Thanks in Advance!
ssharish
Hey guys,
Was just wondering you guys had heard of any Memory managment tools for windoes. Like Valgrind for Unix platform.
Thanks in Advance!
ssharish
Life is like riding a bicycle. To keep your balance you must keep moving - Einstein
Coverity tool is good!
1. Coverity is a static analyzer, not a memory debuggerOriginally Posted by pc_doctor
2. It costs like $15,000 a year (at least that's what we pay)
We've been over this before... Really, there are no good free memory debuggers for Windows. All the good tools are commercial. IBM Rational Purify (not sure if "Rational" is even part of the name anymore) could be gotten for $500 or so, which is relatively cheap
Code://try //{ if (a) do { f( b); } while(1); else do { f(!b); } while(1); //}
I've used both the tools which you guys mentioned, IBM Rational Purify and Coverity. Purify used to be a Telelogic tool and then bought over by IBM. But yeah it not freely available and Coverity, applied for a free trial, and guy from customer service from coverity called me to help out, and asking me the confidential information of the company which I really can’t speak about.
It would have been so much easier if the project was developed on UNIX platform
~ssharish
Life is like riding a bicycle. To keep your balance you must keep moving - Einstein
At work, from time to time we take our software and run it on a Linux machine using Valgrind and Wine. This is actually fairly well supported by the Valgrind folks.It would have been so much easier if the project was developed on UNIX platform
EDIT: Also, as far as I know the Coverity people don't FORCE you to tell them anything. Our software is entirely secret and they didn't ask any questions...
Last edited by brewbuck; 12-07-2009 at 07:22 PM.
Code://try //{ if (a) do { f( b); } while(1); else do { f(!b); } while(1); //}
Insure is another static analyzer and DevPartner has some tools as well. I really do not like either of them due to the insane number of false positives.
But you can do decent memory debugging via the debug CRT if you are using MSVC. The debug CRT will allow you to break on certain allocations, pinpoint which allocations are leaks (with some minor setup on your part), dump blocks of allocation to output, etc, etc.
At Sony we did WinXP/Linux/GameOS (PS3) coding and always do the bulk of the code as cross-platform. That way we can leverage tools like Valgrind on a proper platform and then if things went wonky on the other platforms the possibility space was by definition quite small since the platform-specific stuff was minimal....
