I have a DIY file synchronisation script that worked fine under CLISP 2.47 but would randomly crash under CLISP 2.48 and later. I tracked this down to a particular file. (OS:FILE-INFO this-file) would completely crash CLISP. The file looked pretty normal until I noticed that its "modified date" was somehow set to 1 January of 2098. I downloaded a program called SetFileDate, set modified date to today, and voila, OS:FILE-INFO no longer crashes on it.
Still, while my data was possibly corrupt, it shouldn't result in CLISP outright crashing, and it didn't in 2.47.
My OS: Windows XP SP3
GNU CLISP 2.49 (2010-07-07) (built on STSst063.jenty.by [126.96.36.199])
Software: GNU C 3.4.5 (mingw-vista special r3)
gcc -mno-cygwin -O2 -W -Wswitch -Wcomment -Wpointer-arith -Wimplicit -Wreturn-ty
pe -Wmissing-declarations -Wno-sign-compare -Wno-format-nonliteral -O2 -fexpensi
ve-optimizations -falign-functions=4 -D_WIN32 -DENABLE_UNICODE -I/usr/local/incl
ude -DDYNAMIC_FFI -DNO_READLINE -DNO_GETTEXT -I. -L/usr/local/lib -ltermcap /us
r/local/lib/libavcall.a /usr/local/lib/libcallback.a -luser32 -lws2_32 -lole32 -
loleaut32 -luuid -L/usr/local/lib -lsigsegv libgnu_cl.a
SAFETY=0 HEAPCODES STANDARD_HEAPCODES GENERATIONAL_GC SPVW_BLOCKS SPVW_MIXED TRI
(REGEXP SYSCALLS I18N LOOP COMPILER CLOS MOP CLISP ANSI-CL COMMON-LISP LISP=CL
INTERPRETER SOCKETS GENERIC-STREAMS LOGICAL-PATHNAMES SCREEN FFI UNICODE
BASE-CHAR=CHARACTER PC386 WIN32)
C Modules: (clisp i18n syscalls regexp)
User language: ENGLISH
Machine: PC/386 (PC/686)
Log in to post a comment.