When GHDL returns with a non-zero return code (e.g. for a syntax error), the TCL scripting doesn't catch this error in a clean way and dies.
ghdl: compilation error
child process exited abnormally
while executing
"exec $ghdl -a --std=${VhdlShortVersion} -fsynopsys -Wno-hide --work=${LibraryName} --workdir=${GHDL_WORKING_LIBRARY_PATH} {*}${VHDL_RESOURCE_LI..."
(procedure "vendor_analyze_vhdl" line 19)
invoked from within
"vendor_analyze_vhdl ${VHDL_WORKING_LIBRARY} ${NormFileName} ${OptionalCommands}"
(procedure "analyze" line 15)
invoked from within
"analyze ramp.vhd"
(file "../src/ramp.pro" line 14)
invoked from within
"source ${NormName} "
(procedure "include" line 34)
invoked from within
"include ${Path_Or_File}"
(procedure "build" line 50)
invoked from within
"build ../src/ramp.pro"
(file "run.tcl" line 6)
Expected behavior:
catch child process terminations with non-zero exit code
report an internal simulator error
note caught error in HTML reporting.
exit analysis in a clean way without TCL call stack
When GHDL returns with a non-zero return code (e.g. for a syntax error), the TCL scripting doesn't catch this error in a clean way and dies.
Expected behavior: