[cmucl-help] Re : Disabling the automated code deletion when compiling.

[Raymond Toy]

On 11/2/10 3:13 PM, Rémy wrote:
> I am afraid that snippets from code and logs will not be very efficient to track 
>
> down the problem. The disappearance of important features of the program is 
> quite ubiquitous and the code itself is very dense. Anyway, here is an example 
> of an 'unfortunate' code deletion.

To understand what's going on, I would need to see query and
prompt-read.  It seems prompt-read is creating a symbol where a string
was expected.  It also seems as if prompt-read and/or query are
inlined.  That seems unnecessary for functions that appear to wait for
user input.

It would certainly help in figuring this out if you looked at the notes
to see what the problem really is.  They seem rather serious if you're
feeding a symbol where a string is expected.
>
> If my hypothesis of type errors causing inappropriate code deletion was wrong, 
> what could in your opinion cause the software to progressively lose its 
> features, from cmucl 18c to 20b?
Loss of features is in the eye of the beholder. :-)
> Extra question: I try to compile with various version, to determine when the 
> features exactly start to fade, and the following happens (with version <19):
> I use a Makefile, with this instruction:
>
> tps_compile:    bin lisp tps-compile.lisp make_tps_sys 
>     @date
>     @/bin/sh -ec 'echo "(load \"../tps-compile.lisp\") (core:exit-from-lisp)"' | 
> (cd bin; $(lisp))
>
> and then a Segmentation Fault Occur, while writing this line in the shell does 
> work properly.
>
> /bin/sh: line 1: 11953 Segmentation fault      cmucl18
> make: *** [tps_compile] Error 139
>
> Do you have a clue of what the problem is?
No clue.  I tried a simple makefile and it works for me with 18c.

Ray