Number: 582

Date: 10-Apr-84 10':41':47

Submitter: Sannella.PA

Source: Halvorsen.pa

Subject: STACKOVERFLOW UNDER \10MBWATHCER

Lisp Version: 

Description: '
Date':  7 Apr 84 20':57 PST'
From': Halvorsen.pa'
Subject': Lisp': STACKOVERFLOW UNDER \10MBWATHCER'
To': LispSupport.pa'
cc': Halvorsen.pa'
'
Lisp System Date':  6-Apr-84 18':33':24'
Machine': Dandelion (Halvorsen)'
Microcode version': 24,4'
Memory size': 17777'
Frequency': Once'
Impact': '
When PHYLUM was uncommunicative'
'
-----'
'
Date': 10 Apr 84 11':23 PST'
From': vanMelle.pa'
Subject': Re': AR 582': STACKOVERFLOW UNDER \10MBWATHCER'
In-reply-to': LispSupport.pa''s message of 10 Apr 84 10':42':17 PST (Tuesday)'
To': LispSupport.pa'
cc': vanMelle.pa, cooper.pa, Halvorsen'
'
Since all processes share the same collective stack space, Stack Overflow often "strikes" a process other than the real culprit.  Barring further evidence, I shall assume that is true in this case as well, and Decline the Ar.'
'
LispSupport': 10MBxxx stuff is "low-level Ether", not "NS protocols" (don''t confuse the speed of the ethernet with the type of traffic it carries); no need to attn Cooper on these.'
'
AR': Wish': Make Stack Overflow error happen in the process with the deepest stack.  OS/Processes, Perhaps, Moderate, Annoying, attn me.'
'
	Bill'


Workaround: 

Test Case: 

Edit-By: Sannella.PA

Edit-Date: 10-Apr-84 15':22':27

Attn: 

Assigned To: 

In/By: 

Disposition: 

System: Communications

Subsystem: Other

Machine: 

Disk: 

Microcode Version: 

Memory Size: 

File Server: 

Server Software Version: 

Difficulty: 

Frequency: Once

Impact: Moderate

Priority: Perhaps

Status: Declined

Problem Type: Bug

Source Files: