🎉 Celebrating 25 Years of GameDev.net! 🎉

Not many can claim 25 years on the Internet! Join us in celebrating this milestone. Learn more about our history, and thank you for being a part of our community!

Untitled

posted in DruinkJournal
Published April 24, 2007
Advertisement
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...
Previous Entry Untitled
Next Entry Untitled
0 likes 0 comments

Comments

Nobody has left a comment. You can be the first!
You must log in to join the conversation.
Don't have a GameDev.net account? Sign up!
Advertisement
Advertisement