Well, it looks like I spoke too soon. Because the compile time in the 2004_04 snapshot was so long, I had tried saving part of the application with purification turned on and it worked. From this I extrapolated that purification was working in the 2004_04 snapshot. Over the weekend, I tried letting the application build go to completion; purification dumps
core just like in previous versions of cmucl (18e, 2003_12). So the current state is: - purify works fine in "small situations" in all versions of cmucl that I have tried - purify dumps core when I try the whole application - non-purify works fine for the whole application in 18e and the 2003_12 snapshot - non-purify fails with a div by 0 in 2004_04 Anyone have suggestions on how to debug this problem? Thanks. -bill- William Brew wrote: > Raymond Toy wrote: > > > >>>>> "William" == William Brew <[EMAIL PROTECTED]> writes: > > > > William> As noted in a previous message, the problem only happens when :purify > > NIL > > William> is used when saving. > > > > I'm not familiar at all with the options to save, but is there a > > reason you want to have :purify nil? The default is T. > > The reason is that previously, :purify t caused a core dump when saving the > application (this is where this conversation started). I had not changed the > application's build code to use :purify t. If :purify t works now, then I will start > using it and I can make progress. > > However, there does appear to be a bug with :purify nil. > > -bill-
