Number: 1022

Date:  8-May-84 11':19':17

Submitter: Sannella.PA

Source: halvorsen.pa

Subject: Stack overflow under \HANDLE.NS.ROUTING.INFO (see ar 619)

Assigned To: 

Attn: 

Status: Declined

In/By: 

Problem Type: Bug

Impact: Annoying

Difficulty: Hard

Frequency: Once

Priority: Unlikely

System: Communications

Subsystem: NS Protocols

Machine: 

Disk: 

Lisp Version: 

Source Files: 

Microcode Version: 

Memory Size: 

File Server: 

Server Software Version: 

Disposition: 

Description: '
Date':  7 May 84 11':37 PDT'
From': halvorsen.pa'
Subject': Lisp': Stack overflow under \HANDLE.NS.ROUTING.INFO'
To': LispSupport.pa'
cc': halvorsen.pa'
'
Lisp System Date': 26-Apr-84 18':56':44'
Machine': Dandelion (204#13#)'
Microcode version': 24,4'
Memory size': 17777'
Frequency':  Once '
Impact': Annoying'
'
What can I say,  out of the blue.  A long time ago I had a lot of listfiles processes going at the same time because lispprint didn''t respond,  but I had killed all of them about 1 hour before.'
'
'
'
Kris'
'
Date': 14 May 84 12':38 PDT'
From': vanMelle.pa'
'
Thanks for the report, but I''m going to have to decline this one.  There is no recursion, and not even any deep function calling, under \HANDLE.NS.ROUTING.INFO, so it is unlikely to be the culprit.  As I''ve mentioned, the stack overflow break is not guaranteed to happen in the process that was "guilty" (see Ar 619': Make stack overflow happen in process with deepest stack).'


Workaround: 

Test Case: 

Edit-By: vanMelle

Edit-Date: 14-May-84 12':40':39