Re: interrupt signal in MSW

Hi,

Gunter Königsmann wrote:
><Here I press ctrl+Break>
>*** - handle_fault error2 ! address = 0x74541739 not in [0x61a92af8,0x61cc0000)!
>SIGSEGV cannot be cured. Fault address = 0x74541739.
Please file a clisp bug report about Ctrl-Break. That is not normal behavior.

>C:\maxima-current\bin>maxima -l clisp
Would it also dump core if you invoke the clisp.exe binary directly?

The expected behavior is:
 [1]> ((lambda()(declare (compile)) (loop)))
[Ctrl-Break]
Bye. ; see, no core dump, just quit()
C:\>

>[...] if there is lisp code necessary other than the code that catches SIGINT on linux.
You lost me. Are you talking about behavior in Microsoft Windows (MSW) or on Linux?
Or are you running clisp inside Wine?
Or running a UNIX-style build, i.e. within Cygwin unix simulation on Microsoft Windows?
You didn't tell us what version of clisp you're running.
https://clisp.sourceforge.io/impnotes/clisp.html#bugs

http://andrejv.github.io/wxmaxima/develop.html
references Wolfgang Dautermann's daily builds for MS-Windows:
https://wolfgang.dautermann.at/maxima/nightlybuild/logfile-share-testsuite-clisp.txt      /home/maxima/.maxima/binary/branch_5_41_base_358_gc894ecb/clisp/2_49__2010_07_07___built_3605577779___memory_3734727371_/share
Clisp 2010? Please ask the guys to try and benefit from the recent improvements to clisp's source.
It would make little sense to file a clisp bug report against a 2010 version.

Regards,
	Jörg Höhle
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
clisp-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/clisp-list