Re: [MiNT] AES-calls without appl_init

["Helmut Karlowski" <helmut.karlowski@ish.de>]

J. F. Lemaire wrote:

> > 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=3D0;
> > if(x)
> > =A0 =A0 =A0 =A0print x=3Dx;
> >
> > you would get x=3D0 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.

As mono says there is a memcpy, which can copy multiple bytes with a single assembler-instruction, and the
memory-violation probably comes after that instruction, not before, which would
explain why it still damages the system.

> > Porthos crashes MiNT 1.18, 1.16, MyAES, MiNT/EmuTOS, EmuTOS alone on aran=
> ym.
>
> Then it looks like the perfect test case :-)

Yeah - thanks :)

-Helmut