Open pamoroso opened 3 months ago
From the graphical break window for the TYPE-MISMATCH, left button in the stack trace to select VStatsSpace-Read then middle button there to select Display Edit, answer Y to "do you want to LOADFROM PROP ...". Looking at the source for that function reveals that it's going to use the result of (STORAGE.LEFT)
as a SPACEDATA
record. So, in an Interlisp exec you can (INSPECT (STORAGE.LEFT) 'SPACEDATA)
and see:
and looking at that you'll see that the ATOMFRAC
is NIL - thus the error trying to multiply it by 100.
I suspect the definition of (STORAGE.LEFT)
changed at some point.
You can see in your output that the file came from Hans Koomen - "{FireFS:CS:Univ Rochester}<Koomen>LispUsers>Lyric>VSTATS.;12"
- when he wrote it for the Interlisp Lyric release. It would not surprise me at all if the result of (STORAGE.LEFT)
changed between Lyric and Medley, when the atom space got much larger.
This doesn't solve the problem, but is an example of how to debug.
Very useful, thanks.
with the introduction of 4-byte atoms, there is no longer a difference between storage left for atoms (symbols) vs storage left for anythhing. I remember patching STORAGE (and \MAPMDS) to fix several problems (pr a80788201ffd4) but this looks like a case I missed.
Describe the bug
When loading the VSTATS LispUsers module I get a partially rendered program window and a break window with the error:
To Reproduce
Steps to reproduce the behavior:
Initial Exec
, selectInterlisp
Run Medley
(FILESLOAD VSTATS)
Expected behavior
The VSTATS program window is fully rendered with no errors.
Screenshots
The full desktop with the break window and the partially rendered VSTATS window:
Context (please complete the following information):
Additional context
The transcript of a debugger session: