Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
HUGE MEMORY LEAK pinpointed!
MortenMacFly:
BTW guys; In wxScintilla there are at least two delete's instead of delete[]'s, too. Should we fix that?!
Edit: Don't worry: It's only in my wxScintilla version (1.71.1) the one from SVN seems to be OK though... I should file a bug report to the wxScintilla authors...)
Grom:
If you will continue in the same way - that will be one more studio :lol:.
rjmyst3:
--- 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. It would be much easier to use wxWidget's built-in memory leak search features.I remember that when using wx with Visual Studio, such things was turned on automatically and gave nice reports at the end of execution.
BYO
--- End quote ---
valgrind does not require a recompile of anything - it is not intrusive. As long as the executable has debugging symbols it will work.
byo:
--- 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 ---
Hmm, that's really nice :) Maybe I've confused it with something else or used very early release in the past so I could swear that it redeclare new/free :oops:.
BYO
killerbot:
idea : valgrind plug-in in linux, which allows you to run the debug target.
I have never used it, so maybe the idea is not even possible, dunno. But this would be super cool ...
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version