On Apr 23, 2006, at 8:20 PM, Alfred Van Hoek wrote:
When a plugin is compiled with Xcode 2.2.1 quitting a test app
compiled for Mach-O leads to:
Runtime Error 4: Failed Assertion
Location: dump.cpp 178
Failure Condition: 0
Failure Message: "overwrote end of block"
After the Destructor of the plugin-control is called.
When a plugin is compiled with CW-10, quitting a test app compiled
for Mach-O does not lead to this failed assertion.
Closing the window, instead of quitting: the same behavior. Making
sure that the destructor is not called by internally giving the
control an extra refcount, does not lead to the Assertion.
How to tackle this?
You have memory corruption going on. At some point, you're
overwriting the memory allocated to your plugin control. REALbasic
checks some guard words at the beginning and end of memory
allocations, and those guard words were changed, causing this assertion.
When the control lives on the window it has a refcount of 2,
similar to a canvas. Could be Xcode 2.2.1, anybody else experience
this Assertion?
I doubt it's Xcode. It could be that your plugin control's data
structure is different-sized in Xcode than it is in CodeWarrior. Of
course, that would only be an issue if you have both a PEF and Mach-O
part.
HTH,
Jon
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
