[Freemint-list] shel_write() causing memory violation?

Helmut Karlowski helmut.karlowski at ish.de
Thu Jan 12 02:01:42 MSK 2017


Am 11.01.2017, 23:50 Uhr, schrieb Miro Kropáček:

>>
>> > You must try it without fVDI / NVDI to see memory violation. If you  
>> try
>> it
>> > with fVDI/NVDI, you'll get "only" corrupted window. With my fix
>>
>> You mean this:
>>
>> 22:33:10: pid 13 (tw-call): ILLEGAL INSTRUCTION: User PC=2592CE
>> (basepage=257400, text=257500, data=26E78C, bss=26F110)]
>>
> Wow, for me it's always toswin2.app which causes memory violation. I see  
> a
> normal ALERT, nothing like ILLEGA INSTRUCTION in the console.

That was too early. I can only run teradesk without f/NVDI on hatari -  
somehow on aranym/EmuTOS the redraw does not work in the teradesk-windows.

On hatari I had the wrong build (not 000). Now with the 000-toswin2 I get  
the same behaviour as on aranym+fVDI (the error-window).

I have some uncommitted changes in shel_write and a patched toswin2. Would  
be interesting if any of these matter.

> Guess I'll wait until I see your toswin2-patch.
>>
> Regarding this particular bug, the "patch" is literally changing "1" to  
> "0"
> in shel_write() call in tw-call.c. I'll post it in a few days when I'm  
> done
> with fixing other (minor) issues.

Fine.

--



More information about the Freemint-list mailing list