|
|
|
|
| Re: Crash in tt.dll [message #472370 is a reply to message #472366] |
Mon, 30 July 2012 08:01   |
 |
danpaul88
Messages: 5795
Registered: June 2004
Location: England
Karma: 0
|
General (5 Stars) |
|
|
| StealthEye wrote on Mon, 30 July 2012 15:28 |
This is very weird, it ended up calling a dtor for an object while still running its ctor. Unless you hook Set_Object_Dirty_Bits in some plugin or something, I can't see how this happened.
|
class Object
{
Object::Object
{
delete this;
}
Object::~Object
{
printf ( "BOOM!");
}
}
[Updated on: Mon, 30 July 2012 08:02] Report message to a moderator |
|
|
|
|
|
|
|
|
|
| Re: Crash in tt.dll [message #472462 is a reply to message #472202] |
Tue, 31 July 2012 07:52 |
StealthEye
Messages: 2518
Registered: May 2006
Location: The Netherlands
Karma: 0
|
General (2 Stars) |
 
|
|
danpaul88, it looks sensible for constructing the object, not for destructing it. I can't think of why it would destroy the object, but it would be strange if the dtor appeared on the stack at that point coincidentally too. My guess is that somehow the vtable (or pointer to vtable) was messed up, and it called the dtor instead of Set_Object_Dirty_Bits. This is still quite unlikely though.
BlackIntel admin/founder/coder
Please visit http://www.blackintel.org/
[Updated on: Tue, 31 July 2012 07:52] Report message to a moderator |
|
|
|
Search
Help
Members
Register
Login
Home
It seems to have jumped right from the ctor to the dtor for no apparent reason/cause.
