[Oberon] PO2013 - Infrequent TRAPs
chris at cfbsoftware.com
Sat Jun 13 23:57:53 CEST 2020
Which PO2013 Disk image did you start with? (source and date)
Can you describe any sequence of steps,
1. from initial boot time and
2. on a system which uses all the latest code from the www.projectoberon.com
3. which doesn't include any of your modifications to the latest code
that reliably reproduces any of these problems?
> -----Original Message-----
> From: Oberon [mailto:oberon-bounces at lists.inf.ethz.ch] On Behalf Of Tomas
> Sent: Sunday, 14 June 2020 12:42 AM
> To: Oberon at lists.inf.ethz.ch
> Subject: [Oberon] PO2013 - Infrequent TRAPs
> I know, this has been my on-and-off topic, here it is again.
> I keep record of traps I occasionally got, when working on new modules.
>  When compiling does not finish
> LED(21H) ==> Oberon.GC mark does not pass
>  When unloading fails
> LED(27H) ==> Oberon.GC scan does not pass
>  When executing commands, e.g. ShowModules Position 8280 TRAP1 in
> Modules REPEAT s[k] := ch; (* <== array index *)
>  When loading a file
> Position 6656 TRAP4 in Files
> WHILE (buf.apos # pos) (* <== buf is NIL *)
> I do quite a bit of unloading, before I get things done, Is well possible
> then I smash the heap somehow?
> I am surprised that on some rare occasions I even got  on freshly
> system, and the first thing was to recompile a module.
> I have experimented with ORB object allocation, class, exno, lev: as BYTEs
> vs INTEGERs.
> With INTEGERs,  appears less frequent, than BYTEs, but that's only an
> observation, is most likely not the reason.
> Tomas Kral <thomas.kral at email.cz>
> Oberon at lists.inf.ethz.ch mailing list for ETH Oberon and related systems
More information about the Oberon