Quoting Arnim Laeuger <[EMAIL PROTECTED]>:

> Hi,
>
> At the moment my testbench throws a bound check failed error after some
> us simulation time (GHDL 0.25):
>
> ./tb_zefant_xs3_behav_c0:error: bound check failed (#1)
> ./tb_zefant_xs3_behav_c0:error: simulation failed
>
> Neither reference to a source file nor to a line number.
> Is there a better way to identify the problematic code other than
> looping through disable-compile-run iterations?
Yes.  Analyze with -g option (debug).
Run your design under gdb, set a breakpoint at __ghdl_fatal.  This function
is invoked after the error message.  Then use where/bt commands to display
error line.

Hopes this helps!
Tristan.

_______________________________________________
Ghdl-discuss mailing list
[email protected]
https://mail.gna.org/listinfo/ghdl-discuss

Reply via email to