At some point during the project cycle I created a bug in my program that causes both the built and debug app to throw up a "Failed Assertion" dialog on occasion. It reports the error as "array.cpp:70 0" .
It occurs semi-randomly when running various image manipulation methods. I've tried sprinkling my project with debug code in order to determine what's going on, I've tried profiling it with Shark and also with the SlayFire tools. All of this is to no avail. Pressing the OK button throws up the dialog again immediately, and the Quit button doesn't do me any good debug-wise obviously. I've been able to gather that Failed Assertions are bugs in RB. The project is in RB5.5.4 and moving it to RB2006 is not an option. So obviously it's a bug and I have to find out a way to work around it, but how? So my question is, does anyone know what this error means? I'd guess it has something to do with arrays? Any help would be appreciated. Thank you, ~ Tomis Erwin __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ 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>
