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

[Miro Kropáček]

On 9 January 2017 at 00:36, Thorsten Otto <admin at tho-otto.de> wrote:

> Yes, but it is started from XaAES, not from your application (if $TOSRUN is
> set to tw-call.app). And XaAES starts it only for TOS (aka non-graphic)
> applications. By doing that it forwards your arguments to tw-call.app,
> which
> in turn forwards it to toswin2. If you do a shel_write for a GEM
> application,
> neither tw-call.app nor toswin2 will be involved.
>

OK, you may want to explain it even in more detail, my mind is perhaps
stalled. ;-) I have a .TOS/.TTP application. I want to run it in XaAES.
XaAES uses $TOSRUN (tw-call.app) to start my application. I noticed that if
toswin2.app is not already running, starting my .TOS/.TTP application ends
with memory violation of *toswin2.app*.

So what do I do? I debug toswin2.app and find out that it crashes in
app_init(). I debug CFLib's app_init to find out it crashes on v_opnwk().
So I write a tw-call.app & toswin2.app "clones" to demonstrate the problem.
The "clones" crash in the same circumstances as the originals. You're
saying my test case is not correct. Why?



-- 
MiKRO / Mystic Bytes
http://mikro.atari.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.atariforge.org/pipermail/freemint-list/attachments/20170109/84c449e7/attachment-0001.html