J
John Fullman
I have an application with a class that just doesn't seem to like
destroying...
I have a member that is stored on the heap and it is deleted in the
destructor.
When I run the app in debug mode, I break at the destructor and the
member is still active on the heap. When I step through the delete, it
throws an exception saying that there's nothin' to delete. Wierd.
If it's worth anything, the class in question is imported from another
DLL using __declspec(import) and is cannonical (ie. has a default
constructor, copy constructor, = operator, and destructor)
Has anyone seen this behavior before or am I just doing something wierd
in my code somewhere that I don't see???
destroying...
I have a member that is stored on the heap and it is deleted in the
destructor.
When I run the app in debug mode, I break at the destructor and the
member is still active on the heap. When I step through the delete, it
throws an exception saying that there's nothin' to delete. Wierd.
If it's worth anything, the class in question is imported from another
DLL using __declspec(import) and is cannonical (ie. has a default
constructor, copy constructor, = operator, and destructor)
Has anyone seen this behavior before or am I just doing something wierd
in my code somewhere that I don't see???