Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
HUGE MEMORY LEAK pinpointed!
MortenMacFly:
--- Quote from: rjmyst3 on June 20, 2007, 09:53:26 pm ---valgrind does not require a recompile of anything - it is not intrusive. As long as the executable has debugging symbols it will work.
--- End quote ---
Now that we have that topic: Does anyone know something similar (and free) for Windows?!
--- Quote from: killerbot on June 20, 2007, 10:17:59 pm ---idea : valgrind plug-in in linux, which allows you to run the debug target.
--- End quote ---
Vote++. ;-)
With regards, Morten.
Der Meister:
--- Quote from: byo on June 20, 2007, 05:08:32 pm ---
--- Quote ---Also, maybe someone with the required knowledge could run C::B through valgrind or similar?
--- End quote ---
That would require some knowledge since wxWidgets would have to compiled with valgrind first.
--- End quote ---
No, this should not be necessary. At least it was not as I hunted some memory leaks in Code::Blocks with valgrind more than one year ago.
--- Quote from: Biplab on June 20, 2007, 05:32:58 pm ---Couple of Intel's tools are now free for Non-commercial use on Linux. Can anyone tell us whether Intel VTune Performance Analyser be used to detect Memory Leak or so? :)
--- End quote ---
No, I can't tell you anything about VTune but I would guess that you have to compile Code::Blocks with the Intel Compiler to use this program. And last time I tried to compile Code::Blocks with icc I had to fix quite a lot of issues to get it compiled. And if I remember correctly I was not able to run it after compilation finished. Don't know why, I had given up at this point and just fixed a few things for which the compiler showed some warnings.
Unfortunately Code::Blocks heavily relies on gcc and because of this it is not really possible to use tools for other compilers like VTune or the DevPartner Profiler which uses the Microsoft Compiler.
killerbot:
insider information.
DevPartner/BoundsChecker (Numega/Compuware) should be coming to linux and gcc ...
DevPartner is really good. It helped me spot memory leaks in code from a colleague today very quickly.
EDIT : just read the quick starters guide of valgrind. Some basic stuff should be up and running quickly.
- start the valgrind run command of our 'to-be' plugin
- select the target to (eventually warn if not a debug ('-g') build)
- launch valgrind with the correct arguments (command line arguments can be taken over ??are they exported in the sdk ???)
- capture all the output of valgrind and dump them in a special valgrind message panel [in the future parse and have a valgrind messages list, so double click thakes you to the code line, like with build message list]
Der Meister:
--- Quote from: killerbot on June 20, 2007, 10:27:59 pm ---insider information.
DevPartner/BoundsChecker (Numega/Compuware) should be coming to linux and gcc ...
--- End quote ---
Where did you get these information? :shock:
--- Quote from: killerbot on June 20, 2007, 10:27:59 pm ---DevPartner is really good. It helped me spot memory leaks in code from a colleague today very quickly.
--- End quote ---
Yes it is. Actually, I only used the profiler, but this one is *really* nice. With it's help I got huge speed improvements for my little raytracer. Would probably be nice to run it on Code::Blocks.
Just another comment to valgrind: Running Code::Blocks in valgrind was really easy. If I remember correctly I just used a few command-line options to get more output but then it worked really well and most of the time even provided quite accurate line numbers if it found some problem.
But: Simply starting Code::Blocks in valgrind took ages. Should have been around 5 minutes (!) on my Pentium 4.
killerbot:
I got this info from a compuware sales guy. But it is not finished yet, they are working on it.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version