• Advertisement
Sign in to follow this  

Freebie Memory Leak Tool for VS C++ 6?

This topic is 4727 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Hi, we've got a large legacy application at work thats leaking memory a bit. I was just wondering if anybody has any free alternitives to BoundsChecker for Visual Studio 6 (or I suppose 2003 but we've not converted the project because it's a bit nasty). We all have fully licenced VS 2003 Enterprise Edition too, and it may be that something already exists in there that we're missing. At the moment the project is in VS C++ 6 though, and would be a real pain to convert (because it's not your normal project). We've found a neat program that's helped a bit called "Debuggy", but something that lets you step in and out of source code files as well would be awesome. http://web.vip.hr/inga.vip/index.htm I did do a search on the forum before posting and found nothing relevant, but excuse me if I am repeating something recently posted. Thanks for any links etc! Paul

Share this post


Link to post
Share on other sites
Advertisement
Look up _CrtSetDbgFlag in the MSDN. When the application exits, it lists all the memory that wasn't freed together with its allocation number. Run the program again, this time calling _CrtSetBreakAlloc (<the number reported previously>) and the program will stop when the leaky memory is allocated. You should then be able to quickly determine why it isn't being freed.

Skizz

Share this post


Link to post
Share on other sites
Quote:
Original post by MENTAL
Flui d Studios Memory Manager

Been using it in all my projects for a very long time and I haven't yet found a bug in it.
Yup, I can recommend this too. Unfortunately, it only works with single threaded applications. If you try using it in a multithreaded app without modifying it to add enter critical sections or something, then you'll get all sorts of weird bugs.

Share this post


Link to post
Share on other sites
Try my advanced modification of Fluid Memory Tracker @ http://openglgui.sourceforge.net/mmgr_tut1.html
http://openglgui.sourceforge.net/mmgr_tut2.html

Share this post


Link to post
Share on other sites
Unfortunetly that Fluid tracker requires a ton of changes to the application source to get it working because it's an MFC app. Also I'll take Evil Steve's word for it as far as threading issues are concerned... threading might even be part of the memory leaking problem so we need a memory manager that can handle threads.

I'll take a look at that thing you were pointing at HellRiZZer - but my guess is that it probably comes with similar constraints, props for suggesting though!

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement