Bug or Expected Behavior with Compiled Code
- Posted by euphoric (admin) Jun 28, 2011
- 1457 views
I have a program that crashes with an unhelpful message when the code is compiled. This might be the way it has to be, but I thought I'd ask...
When I run the program interpreted, I get a normal error message:
C:\Users\Owner\My Programs\add_inventory\add_inventory.exw:111 in procedure main() slice starts past end of sequence (1 > 0) ... called from C:\Users\Owner\My Programs\add_inventory\add_inventory.exw:248
When I run it compiled, I get a dialog box whose title is "Assertion Failed." The body of the dialog box has one line that reads, "size >= 0, function NewS1, file be_alloc.c, line 818."
Line 111 of the source is:
vTime = vTime[1..6]
and vTime = {} at the time of the error.
Is this expected crash behavior for the compiled code? Does the error message of the compiled program have to be this useless (to me), or could it specify the actual error (trying to access non-existent sequence element[s])?
