[Oberon] trap output problems

[Peter Matthias]

Hi Jan,

Am 29.10.2015 um 16:52 schrieb Jan de Kruyf:
> Hallo Peter,
>
>  > I suppose the best way would be to send me the source to reproduce
> the text corruption fault. You also can use ARM and MIPS targets via
> qemu to check the behaviour.
>
> Here is a barebones module to demonstrate the trap printout problem.
>
> There are 2 pointers, one initialized (S) and one uninitialized (T).

S is not a POINTER but a RECORD.

> You can compile and run it as is. it will trap and give 2 values to
> compare against in the kernel log.

For RECORDS, the type descriptor address is being printed. I suppose the 
address is relative to the static base of the module.

> It looks to me that the problem is in the trap printing routine.

It might be better to show the elements of the record, however, the 
behavior is consistent with Native Oberon.

Regards,
	Peter