Number: 260

Date: 22-Mar-84 11':51':09

Submitter: Sannella.PA

Source: Masinter.pa

Subject: ILLEGAL ARG - NIL under GV.ADDTOITEM

Assigned To: 

Attn: 

Status: Declined

In/By: 

Problem Type: Bug

Impact: Moderate

Difficulty: 

Frequency: Once

Priority: Unlikely

System: Text

Subsystem: Lafite

Machine: 

Disk: 

Lisp Version: 

Source Files: 

Microcode Version: 

Memory Size: 

File Server: 

Server Software Version: 

Disposition: [4/28/84 bvm': declined as non-reproducible]

Description: '
Date': 21 Mar 84 16':59 PST'
From': Masinter.pa'
Subject': Lisp': TWO BUGS'
To': LispSupport.pa'
cc': Masinter.pa'
Lisp-System-Date': 15-Mar-84 00':13':18'
Machine-Type': Dandelion'
'
First bug':Subject': Lisp': GC under TEdit causes 9305'
To': LispSupport.pa'
cc': Masinter.pa'
Lisp-System-Date': 15-Mar-84 00':13':18'
Machine-Type': Dandelion'
'
I dunno if this is DLion microcode or TEdit or a combination of both. Something that TEDIT has on its stack when a GC gets invoked causes the DLion GC to get a 9305. Probably it is trying to reference count on the stack something that isn''t a valid pointer. I guess this is a DLion microcode problem, but it is pretty serious. Could be fixed by either fixing DLion microcode or TEdit, I would guess.'
'
Intermittent, Serious, Attn': Charnley, Sybalsky, Hopefully, Difficulty': Moderate'
'
'
Second bug': '
'
in sending the first bug report, I got an ILLEGAL ARG - NIL under GV.ADDTOITEM. I think the problem was the COPYBYTES from the TextStream to the BSP stream got a NIL as the value of BIN from the textstream. This could be an artifact of the previous report where I had a problem because it crashed in the middle of a GC.'


Workaround: 

Test Case: 

Edit-By: vanMelle

Edit-Date: 15-May-84 16':56':23