Dr. Martin Lehr

note: fot this issue I opened a ticket...

GT.M 6.3: for-loop inside a string to be executed may stop further execution

Hello, this problem was caused by severe kernel bugs in some SuSE Linux versions. Many other programs (for example java) have also been affected by this bug. In the meantime SuSE fixed this bug and Meltdown/Spectre is fully patched. Martin Lehr

Hello all! The Execute command shows some strange results in GT.M 6.3-007. Example: W !,"start" X "F J=1:1:0 W !,J" W !,"stop" Q The output is: start This is wrong! If the following line: W !,"start" X "F J=1:1:0 W !,J" W !,"stop" is executed in direct mode, the output is: start stop This is correct! In GT.M 5.1 the results of this command line are always correct. Martin Lehr

Hi all, by installing an older Linux-kernel (June 2018) the problem is solved!

Hi all, we observe gt.m crashes after these meltdown + spectre patches. System ist SuSe Linux. These crashes are rare events, but typically we see them when there ist high load. After the crash mupip integ sometimes reports errors. On multiprocessor systems now (after meltdown/spectre patsches) the gt.m process switches from one CPU to the other, even under 100% load. In former times this was not the case. Has anybody else seen problems like this?