Pascal Bourguignon <pjb@...> writes:
> I'm generating a core with:
> Which writes 19MB of core vs. 1MB of clisp image:
> Is this normal?
> I guess that compiling my program with (OPTIMIZE (SPACE 3)) would not
> improve significantly the situation, would it?
I guess not; have you tried it? (Note that the majority of the core
file will be taken up by sbcl itself if your program does not
approach sbcl itself in size, so I guess it will not help much.)
> If yes, it could be worthwhile to handle gziped cores:
Well, since the core file is mmap()ed at startup, you'd have to unzip
the core on-the-fly, which would need even more disk space. I can not
think of another solution, but if you can, I'm sure the implementors
will be interested to hear it, or even comment on patches you might
whois DRS1020334-NICAT http://constantly.at/pubkey.gpg.asc
Key fingerprint = C182 F738 6B9A 83AF 9C25 62D9 EFAE 45A6 9A69 0867