Segmentation fault when looping through a Céu vector about ceu HOT 8 CLOSED

There are no recoverable exceptions in Céu, i.e., the program should terminate with the message.
However, the segfault shouldn't happen in any case.

from ceu.

Ok, I just expected the program to escape 42 because of the following example:

var u8[2] foo;

foo = [] .. foo .. [4];
foo = [] .. foo .. [2];
foo = [] .. foo .. [7];

escape 42;

In this case obviously an access out of bounds error appears but the program nonetheless escapes 42:

[application.ceu:5] runtime error: access out of bounds
*** END: 42

So should it always terminate immediately after a runtime error message?

from ceu.

Yes, immediately.
Can you try to compile the final .c with -DCEU_DEBUG ?
I think this is the whole problem. The underlying assert is not being called, which explains the segfault and also why my tests aren't catching such a simple bug.

from ceu.

Sure. This leads to the following output:

(0): 1
(1): 2
(2): 3
(3): 4
[application.ceu:4] runtime error: access out of bounds
a.out: application.ceu:3558: ceu_sys_assert: Assertion `v' failed.
Aborted (core dumped)

from ceu.

Ok. Now the behavior is correct and the error also appears in the correct line.
I'll leave this issue open because of the -DCEU_DEBUG requirement.

from ceu.

Just as a complementary:

Now also the behaviour of the other example is correct...

var u8[2] foo;

foo = [] .. foo .. [4];
foo = [] .. foo .. [2];
foo = [] .. foo .. [7];

escape 42;

now leads to

[application.ceu:5] runtime error: access out of bounds
a.out: application.ceu:3557: ceu_sys_assert: Assertion `v' failed.
Aborted (core dumped)

means that it is terminated immediately after the error message without escaping 42 - as you specified!

from ceu.

Can you confirm if these applications crash with the correct message (even without -DCEU_DEBUG)?

from ceu.

Yes. Both examples crash with the correct assertion message even without -DCEU_DEBUG.

from ceu.