Reverse Engineering RET Homepage RET Members Reverse Engineering Projects Reverse Engineering Papers Reversing Challenges Reverser Tools RET Re-Search Engine Reverse Engineering Forum Reverse Engineering Links

Go Back   Reverse Engineering Team Board > Reverse Engineering Board > Reverse Code Engineering
FAQ Members List Calendar Search Today's Posts Mark Forums Read

Thread Tools Display Modes
Old 06-27-2011, 09:34 AM
blahh blahh is offline
Junior Member
Join Date: Jun 2011
Posts: 2
Default finding out memory leakage from disassembly

A classic case of memory leakage is when you have a Base class `Base`, a child class `Child`, you don't have a virtual destructor and do the following.

Base *b = new Child();
delete b;

Are there any patterns to look for in the disassembly in order to stop such leaks? I ask this in relation to spotting memory leaks for the dangling pointer exploitation technique.
Reply With Quote

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.