Number: 519

Date:  5-Apr-84 12':11':15

Submitter: Sannella.PA

Source: vanMelle.pa

Subject: GCREF should not cause invalid address for pointers out of bounds

Assigned To: vanMelle

Attn: 

Status: Superseded

In/By: 

Problem Type: Performance

Impact: Serious

Difficulty: 

Frequency: Intermittent

Priority: Perhaps

System: Language Support

Subsystem: Microcode

Machine: 

Disk: 

Lisp Version: 

Source Files: 

Microcode Version: 

Memory Size: 

File Server: 

Server Software Version: 

Disposition: 

Description: '
Date':  4 Apr 84 19':34 PST'
From': vanMelle.pa'
...'
259': Comment': if this is a Dandelion ucode problem, it is also a Dolphin/Dorado ucode problem, because they fall into Raid when GC tries to mark the stack bit on a bogus pointer.  So it seems clearly in Tedit''s domain.  On the other hand, you might add an AR wish for all three microcodes, "GCREF should not cause invalid address for pointers out of bounds".'
DLion uCode doesn''t do this.  -- don'
'
DLion uCode does do it, but this AR has been superceded, since the stack parser maps things into a valid range before calling GCREF.

Workaround: 

Test Case: 

Edit-By: Masinter

Edit-Date: 17-Aug-84 12':05':52