Sign in to follow this  
  • entries
    557
  • comments
    1237
  • views
    421061

Untitled

Sign in to follow this  
Evil Steve

41 views

My new method for finding out where these vector-resize memory leaks are coming from:
1. Put a breakpoint somewhere to break to the debugger
2. Open CodeWarrior's memory editor
3. Go to address the leak is at
4. Type "dgfg" over and over until you overwrite all the memoy
5. Remove breakpoint and run code
6. Wait for crash and see where it crashed.

It's worked surprisingly well so far...
Sign in to follow this  


0 Comments


Recommended Comments

There are no comments to display.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now