Bug#676979: sbcl: file nik.lisp for reproduction is included below

Hi! Faheem Mitha writes: > On Wed, 9 Jan 2013, Christoph Egger wrote: >> So actually it either needs to actually dfail to allocate the memory >> or it's platform-specific. I think I get the problem on a amd64 with >> few enough memory to trigger the Heap exhaustion > > Hi Christoph, > > Thanks

Bug#676979: sbcl: file nik.lisp for reproduction is included below

On Wed, 9 Jan 2013, Christoph Egger wrote: Hi! So actually it either needs to actually dfail to allocate the memory or it's platform-specific. I think I get the problem on a amd64 with few enough memory to trigger the Heap exhaustion Hi Christoph, Thanks for taking a look. The develope

Bug#572967: marked as done (Core dump with bus error)

Your message dated Wed, 09 Jan 2013 13:44:29 -0800 with message-id <87obgyjaki@mitoraj.siccegge.de> and subject line SBCL Bus Error has caused the Debian Bug report #572967, regarding Core dump with bus error to be marked as done. This means that you claim that the problem has been dealt with.

Bug#676979: sbcl: file nik.lisp for reproduction is included below

Hi! So actually it either needs to actually dfail to allocate the memory or it's platform-specific. I think I get the problem on a amd64 with few enough memory to trigger the Heap exhaustion Regards Christoph ___ pkg-common-lisp-devel mailin

Bug#676979: Testing on 1.1.3

Hi! I've been running (main 1) on 1.1.3 (kfreebsd-amd64) debian package, it ends with: --- Dynamic space usage is: 524,455,600 bytes. Read-only space usage is: 5,200 bytes. Static space usage is: 3,088 bytes. Control stack usage is:2,656 bytes. Binding stack usage is: