Usage detection after free () on windows. (dangling pointers)

Question

I am trying to detect "Use after free ()" errors, otherwise called "Hanging Pointers". I know that Valgrind can be used to detect "Use after free" errors on the * nix platform, but what about windows? What if I do not have a source? Is there a more efficient program than Valgrind to detect all dangling pointers in a program? Free and open source will be preferred, but I will use a commercial solution if it does its job.

Answer 1

The MSVC debugging memory allocator is already doing this. When you get 0xfeeefeee from dereferencing a pointer, you are dangling. With some luck that will bomb the program.

Answer 2

You can use gflags.exeand Debugging Tools for the Windows , to include the heap verification process:

• http://msdn.microsoft.com/en-us/library/cc265885.aspx

It has been a while since I used this, and I honestly can't remember how well it interacts with the C heap runtime, unlike the Windows heap manager (to ensure that every malloc()/ free()/ new/ deletecall is individually checked )

Free but not open source.

Answer 3

, Valgrind, Microsoft Application Verifier Windows. API, , - :)

Answer 4

Purify . , , .

Answer 5

. CheckPointer, C. , Wndows.

Answer 6

NuMega BoundsChecker . , , ...

Answer 7

DieHard is another alternative worth paying attention to. This is on the HOARDE website, which unfortunately seems to use frames, so you need to look in the left navigation to find DieHard.

Answer 8

Mark a bunch of Windows debugging . This is not open source, but works.

Answer 9

After free () set the pointer to 0 and wait for the fireworks?