Re: [MiNT] AES-calls without appl_init

["J. F. Lemaire" <jflemaire@skynet.be>]

> Sure - that's why I tried to get marathon to work (should do now btw).
> At first I ran it from ext2, and had to rename/copy some files to get it
> starting. I must have done something wrong, which caused it to produce
> the memory-violation. But I tried to stabilize the system to keep it up.
> Really strange things happened, apparently code has been overwritten.
>
> If there is something like:
>
> x=0;
> if(x)
>        print "x="x;
>
> you would get x=0 in the logfile. Also with memory-protection.
>
> Don't know how an app can do that, maybe it comes from MiNT or XaAES.

Maybe compiling Marathon with both AHCC and PureC and compare the
results might give us a clue? I doubt the compiler could be
responsible, but who knows.

> Porthos crashes MiNT 1.18, 1.16, MyAES, MiNT/EmuTOS, EmuTOS alone on aranym.

Then it looks like the perfect test case :-)

Cheers,
JFL
-- 
Jean-François Lemaire