> * In message <200203040432.g244WoR06029@...>
> * On the subject of "Re: [clisp-list] aborting MAKE-ARRAY leaves CLISP in an unstable state?"
> * Sent on Sun, 3 Mar 2002 23:32:50 -0500 (EST)
> * Honorable Carl Shapiro <cshapiro@...> writes:
> please try
> (make-list 10000000)
> do you get the same?
> could you play with the various *PRINT-* vars to determine what makes
> this happen?
> If I break in the printer with *PRINT-LENGTH* set to NIL I can
> reliably cause a segmentation fault on the first try.
I was also interested in *print-pretty*.
So, what is the combination of vars that gets the crash the earliest?
> Sometime today I realized that I had never manually invoked the CLISP
> collector and so I gave it a try, and then did it a second time hoping
> to get a hint as to what the return value signifies.
impnotes.html is your friend...
> I can get a core file, but my clisp isn't compiled with symbols so gdb
> isn't very revealing. I'll try recompiling with symbols tomorrow and
> giving this another try.
I do not observe this in the current CVS, and my hardware is totally
inadequate for intensive configure/build/test cycles, so I would
appreciate it if you could try to use binary search to find out _when_
the bug was introduced.
use CVS - get the earliest revision, check whether the crash is there,
if not - try a revision midway between then and now...
Sam Steingold (http://www.podval.org/~sds) running RedHat7.2 GNU/Linux
Keep Jerusalem united! <http://www.onejerusalem.org/Petition.asp>
Read, think and remember! <http://www.iris.org.il> <http://www.memri.org/>
Please wait, MS Windows are preparing the blue screen of death.