Number: 2137

Date: 11-Sep-84 11':34':40

Submitter: Sannella.PA


Subject: cross version Teleraid doesn''t work': Teleraid ERROR!s if it tries to initialize non-existant atoms.

Assigned To: 

Attn: Masinter, vanMelle

Status: Open


Problem Type: Bug

Impact: Moderate



Priority: Perhaps

System: Language Support

Subsystem: Bootstrapping and Teleraid

Machine: 1132


Lisp Version:  8-Sep-84 01':22':25

Source Files: 

Microcode Version: 5124

Memory Size: 4096

File Server: 

Server Software Version: 


Description: '
Date':  7 Sep 84 20':36 PDT'
Subject': TELERAID broken again'
To': LispSupport'
cc': Masinter'
Foo, TELERAID seems to be broken again -- I notice there is a new RDSYS dated Sep 5, so . . .'
One symptom is a break for IPLUS of NIL under VATOM again.  Another is that when I use TELERAID from an older sysout, to snoop on a DLion running the currnet <LispCOre>Next> sysouts, it merely returns (from TELERAID) doing nothing except returning some random unprintable litatom.  Nope, doesn''t run any error.'
-- JonL --'
Date':  7-Sep-84 21':14':30 PDT'
Subject': cross version Teleraid deson''doesn''t work'
To': LispCore↑'
There''s a problem running TeleRaid between pre-array-bucket and post-array-bucket sysouts. The problem is that TeleRaid wants to initialize the value of variables that don''t exist. If you try to start up TeleRaid and it just pops back with an ERROR! out of the TELERAID call, try setting the variable RDPTRS to NIL and retry.'
(before array-buckets, every sysout had a \FREEBLOCKLIST that TELERAID wanted to initialize, and now there''s \FREEBLOCKBUCKETS. The only reason that TELERAID wants those variables is in case you want to do a VPARSEARRAYSPACE to look at the remote guy''s array space. '
It is a misfeature that teleraid''s atom lookup routine ERROR!''s out rather than returning something.'


Test Case: