Did experience this on the combination Windows/gcl. Now I did experience the same thing on the combination Linux/sbcl: If I start wxMaxima from a terminal and then interrupt it using Ctrl+C one CPU is running constantly thereafter. On my linux/sbcl version I get an endless stream of the following console output in this case:
Did experience this on the combination Windows/gcl. Now I did experience the same thing on the combination Linux/sbcl: If I start wxMaxima from a terminal and then interrupt it using Ctrl+C one CPU is running constantly thereafter. On my linux/sbcl version I get an endless stream of the following console output in this case:
There seems to be no really portable way to catch a SIGSEV or similar, though.