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

Helmut Karlowski helmut.karlowski at ish.de
Thu Jan 12 01:39:49 MSK 2017


---------------------------------------------------
> On 12 January 2017 at 07:43, Helmut Karlowski <helmut.karlowski at ish.de>
> wrote:
> 
> > What exactly are you fixing? Running a ttp from teradesk when toswin2 is
> > not running?
> >
> Yep. .ttp -> tw-call.app -> toswin2.app
> 
> 
> 
> > Just tried that: no problem, except there is an additional window with an
> > incomplete error-message.
> >
> 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)]



> (tw-call.app calls toswin2.app with wiscr = 0 in shel_write()) you'll get
> no such behaviour.
> 
> It's because toswin2.app thinks there are some command line arguments
> whereas there are not. So you see, it's quite a dangerous bug, you can't
> blame solely the caller for that.

Guess I'll wait until I see your toswin2-patch.



More information about the Freemint-list mailing list