Hi,
in the feedback system you will find this filed reports.
http://www.realsoftware.com/feedback/viewreport.php?reportid=etijqgvb
http://www.realsoftware.com/feedback/viewreport.php?reportid=nxdxvccb
Do you using exception blocks in your methods? If not, please try it
and add break points to them.
I hope this helps you a little to find the bug.
Am 17.05.2006 um 23:24 schrieb Tomis E.:
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?
--
Vincent
_______________________________________________
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>
