>>>>> "William" == William Brew <[EMAIL PROTECTED]> writes:
William> ;;; a (room t) just before the end
William> Dynamic Space Usage: 54,126,960 bytes (out of 1,024 MB).
William> Read-Only Space Usage: 22,801,648 bytes (out of 256 MB).
William> Static Space Usage: 2,668,752 bytes (out of 256 MB).
William> Control Stack Usage: 6,032 bytes (out of 128 MB).
William> Binding Stack Usage: 600 bytes (out of 128 MB).
William> The current dynamic space is 0.
William> Garbage collection is currently enabled.
Should be plenty of space available, even with the old limits. I just
tried with McCLIM. Tha'ts not quite as large, but pretty close:
Dynamic Space Usage: 47,328,576 bytes (out of 256 MB).
Read-Only Space Usage: 22,725,528 bytes (out of 128 MB).
Static Space Usage: 2,672,808 bytes (out of 128 MB).
Control Stack Usage: 544 bytes (out of 128 MB).
Binding Stack Usage: 96 bytes (out of 128 MB).
The current dynamic space is 0.
[snip]
William> #0 pscav (addr=0x2800000b, nwords=0, constant=687057392)
William> at ../../src/lisp/purify.c:1168
William> 1168 ../../src/lisp/purify.c: No such file or directory.
William> (gdb) print thing
William> $1 = 2
William> (gdb) print thingp
William> $2 = (lispobj *) 0x28000008
William> (gdb) print header
William> $3 = 687057616
William> (gdb) print count
William> $4 = 687057616
William> (gdb) print vector
William> No symbol "vector" in current context.
William> (gdb) q
William> otwb-dev bbrew 82>
Can you do your own build? I can lead you through it. The reason I
ask, is because this backtrace doesn't make sense to me and I want you
to compile the C files with debugging on, and no optimization.
addr is the NIL object. nwords is 0. Therefore, pscav has nothing to
do. And the fault line is 1168, which is the beginning of the
routine. It would help to know exactly which line it's failing on.
Ray
