Number: 2020

Date: 29-Aug-84 15':32':34

Submitter: le.pasa

Source: Bird.pasa

Subject: Bad recovery from stack overflow

Assigned To: 

Attn: Masinter, VanMelle

Status: Open

In/By: 

Problem Type: 

Impact: Serious

Difficulty: 

Frequency: Everytime

Priority: Perhaps

System: Language Support

Subsystem: Stack and Interpreter

Machine: 1108

Disk: 

Lisp Version: 21-Jun-84 10':50':28

Source Files: 

Microcode Version: 5124

Memory Size: 3071

File Server: 

Server Software Version: 

Disposition: related to AR 2018.'
["Sannella.PA" "29-Aug-84 17':27':46" Status':(New->Open) Priority':(->Perhaps)]

Description: Default recovery procedures from stack overflow are inadequate.  Personal experience and advice from others indicates that a system is highly unreliable unless a (HARDRESET) is performed soon after a stack overflow.  Obviously, it would be desirable to handle stack overflow tidily.  Lacking this, it would be safest to perform the (HARDRESET) automatically.  Stack overflows are, after all, quite common during LISP software development.

Workaround: 

Test Case: 

Edit-By: Sannella.PA

Edit-Date: 29-Aug-84 17':27':48