Auto-zlink works properly when linking a newer version of an M routine after changing $ZROUTINES
Final Release Note
Auto-ZLINK works properly when linking a newer version of an M routine after changing $ZROUTINES. Previously, it could in rare cases terminate the process abnormally with a fatal GTMCHECK error and a core dump. This was encountered in the development environment and was never reported by a user. [#441 (closed)]
Description
Below is a csh script that illustrates a regression in GT.M V6.3-006.
> cat test.csh
rm -rf patch bar.m *.o >& /dev/null
mkdir -p patch
touch bar.m
mumps -run %XCMD 'ZCompile "bar"'; mv bar.o ./patch
mumps -run %XCMD 'ZCompile "bar"'; mv bar.o ./patch/bar2.o
cat > base.m << CAT_EOF
ZLink "bar"
Set \$ZROutines="./patch"
Do ^bar2
CAT_EOF
mumps -run base
The above script produces the following output after integrating GT.M V6.3-006 into the YottaDB mainline.
> source test.csh
%YDB-F-GTMCHECK, Internal YottaDB error--Report to your YottaDB Support Channel
The same script does not produce a fatal error with r1.24 (which only has GT.M V6.3-005 integrated).
Draft Release Note
Auto-ZLINK works properly when zlinking a newer version of an M routine after changing $ZROUTINES. Previously, it could in rare cases terminate the process abnormally with a fatal GTMCHECK error and create a core dump file. [#441 (closed)]