Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development
Code::Blocks SDK documentation
dmoore:
--- Quote from: ollydbg on November 30, 2013, 08:44:56 am ---I would like to see the whether there are some memory leaks in our CB code by linking to msvcrtd.
--- End quote ---
I have used debug_new to find some pretty obscure memory leaks. Not sure how well it would work with wxWidgets apps...
http://sourceforge.net/projects/nvwa/
comsytec:
--- Quote from: MortenMacFly on November 30, 2013, 07:37:47 am ---
--- Quote from: comsytec on November 29, 2013, 04:45:47 pm ---To make easily to switch between build configurations. Somewhere in this forum I mention about it but don't got any positive response for such change of compiler plugin.
--- End quote ---
Did you post a patch on SF.net? (Hopefully its not only for 10.05.)
--- End quote ---
No on SF.net not. In past I posted some package in this forum http://forums.codeblocks.org/index.php/topic,17299.0.html but I got only criticism about unneeded redundant feature for C::B and I not bothered with further. I know these changes not ideal but at least helps to me. Configurations shown on the picture are fixed and to change them requires further development.
comsytec:
--- Quote from: ollydbg on November 30, 2013, 08:44:56 am ---Some links: Using msvcrt debug version (msvcrtd) (with a msvcrtd.a attached in one reply.)
But I still don't know how to use it in current(newer) version of MinGW. @Comsytec: can you show us the details?
I would like to see the whether there are some memory leaks in our CB code by linking to msvcrtd.
--- End quote ---
Ok next week will prepare package with MinGW where it is included for download here. And also must mention about that wxWidgets must be linked with also otherwise it is useless so I must also post updated wxWidgets source. This method solves monitoring of the malloc but not fully the new which can have lot of forms and replacing of debug version of heap allocations is achieved through preprocessing directives.
ollydbg:
--- Quote from: dmoore on November 30, 2013, 02:03:44 pm ---
--- Quote from: ollydbg on November 30, 2013, 08:44:56 am ---I would like to see the whether there are some memory leaks in our CB code by linking to msvcrtd.
--- End quote ---
I have used debug_new to find some pretty obscure memory leaks. Not sure how well it would work with wxWidgets apps...
http://sourceforge.net/projects/nvwa/
--- End quote ---
Thanks, I have tried nvwa before, but I believe that nvwa need to build into wx's source to correctly report all memory leaks. E.g. most GUI window was allocated in user code by new wxXXXX, but released from wx's source.
I found another nice tool: drmemory http://www.drmemory.org/ , which looks good.
Navigation
[0] Message Index
[*] Previous page
Go to full version