Number: 250

Date: 22-Mar-84 10':27':09

Submitter: Sannella.PA

Source: Burton.pa

Subject: Filemap rewrite code should check error type

Lisp Version: 15-Mar-84

Description: '
Date': 21 Mar 84 10':47 PST'
From': Burton.pa'
Subject': Lisp': Filemap rewrite code isn''t checking error type'
To': LispSupport.pa'
Lisp-System-Date': 15-Mar-84 00':13':18'
'
I ^Eed when a function was being fetched from a file to be editted (after the "loading from mumble;81" msg) and the system rewrote the file map for mumble, then fetched the function.  Could the code that traps the error check to see if the error was due to user ^E or (ERROR!) caused by invalid filemap??'
richard'
'
-----'
'
Date': 21 Mar 84 11':07 PST'
From': Burton.pa'
Subject': Lisp': Addendum to filemap making'
To': LispSupport.pa'
Lisp-System-Date': 15-Mar-84 00':13':18'
Machine-Type': Dorado'
'
When I did a MAKEFILE on the file that had had its file map rewritten, the system rewrote it again.'
'
richard'
'
-----'
'
Date': 22 Mar 84 10':48 PST'
From': Kaplan.pa'
Subject': Re': AR 250': Filemap rewrite code should check error type'
In-reply-to': LispSupport.pa''s message of 22 Mar 84 10':28':32 PST (Thursday)'
To': LispSupport.pa'
'
I''m not a filemap expert.  I think JonL was last in there, perhaps Bill or Larry.'
'
But you might add the following complaint':'
'
I had a filemap loaded for FOO;1, then said to PF a function from FOO;2 on a host for which I wasn''t logged in.  Not noticing what was going on, I ctl-Ed while it was asking for the password.'
'
It then went on to do the PF from the FOO;2, but IT USED THE FILEMAP FOR FOO;1.'
'
Don''t know whether this particular problem should be fixed by /REMPROPing the old filemap before starting (under a resetsave), or by having some higher level test (e.g. in PF) about whether the filemap that it gets back is actually the one for the file it was interested in.'


Workaround: 

Test Case: 

Edit-By: Masinter.PA

Edit-Date: 19-Apr-84 16':03':06

Attn: Masinter.pa

Assigned To: 

In/By: 

Disposition: 

System: Programming Environment

Subsystem: File Package

Machine: 

Disk: 

Microcode Version: 

Memory Size: 

File Server: 

Server Software Version: 

Difficulty: 

Frequency: Once

Impact: Annoying

Priority: Hopefully

Status: Open

Problem Type: Design - Impl

Source Files: