🔒 Locked

Tools for checking memory leaks?

Started by csolar Jul 5, 2004 at 12:43 AM 8 replies 1.1k views

Original Post

Jul 5, 2004 at 12:43 AM

Im working on a complicated program that loads a bunch of stuff up at runtime and (hopefully) destroys everything when stopped. The information I mostly use is in the form of poctures and the like. I was wondering if theres a helpful tool out there for me to use to make sure that everything allocated gets destroyed. In otherwords, checks to make sure my program does not have a memory leak. Does anyone know of such a program? And if so, where can I find one? Thanks, Charles

Prozak

217

Prozak

Jul 5, 2004 at 2:01 AM

Fluid Studios

Go to the bottom of that page, click on "MMGR" and download.

Had that source code to your project, it will be an invaluable tool in searching for memory looks.

Raduprv

202

Raduprv

Jul 5, 2004 at 2:05 AM

If you are running Linux, try Valgrind. It's teh r0x!

xiuhcoatl

Jul 5, 2004 at 2:08 AM

Boundschecker used to be pretty good. I was sort of preferential to Purify. Both are a little expensive though...

#dth-0

stay in school

Jul 5, 2004 at 4:39 AM

I like Memory Validator for windows. The free trial is either 2 weeks or 1 month - can't remember. I found it very easy to use.

ibawt

Jul 5, 2004 at 8:31 AM

How about Electric Fence? It's free....or better yet redefine malloc and free to your own functions and just count the number of allocations versus free's.

Raduprv

202

Raduprv

Jul 5, 2004 at 3:32 PM

Quote:
Original post by ibawt
How about Electric Fence? It's free....or better yet redefine malloc and free to your own functions and just count the number of allocations versus free's.

This technique somewhat works for memory leaks, but it's totally ineffective against other type of memory problems, such as memory violations.

ibawt

Jul 5, 2004 at 4:03 PM

Quote:
Original post by Raduprv
Quote:
Original post by ibawt
How about Electric Fence? It's free....or better yet redefine malloc and free to your own functions and just count the number of allocations versus free's.

This technique somewhat works for memory leaks, but it's totally ineffective against other type of memory problems, such as memory violations.

I believe the orignal poster asked for "Memory Leak detection"

Raduprv

202

Raduprv

Jul 5, 2004 at 6:42 PM

Sure, but why not get a tool that does more than that? Memory leaking is relatively easy to detect, as opposed to:
1. access violations
2. reading from unitialized memory

Valgrind solves all those problems, plus many more. But unfortunately it works only on Linux.

Topic Locked

This topic has been locked by a moderator. New replies are not allowed.