Re: [MiNT] analysing syscall.spp

[Konrad Kokoszkiewicz <draco@mi.com.pl>]

Hi Joerg,

> Well, at least the calls for memory allocation handling also modify global
> data (the memory list).

In this case it doesn't hurt anything as long as they're atomic. Anyways,
Malloc() or Mxalloc() rather :-) cannot wrap back to trap handler, so it
doesnt matter if they modify globals or not.

Contrary, a Fopen() can wrap back if a filesystem driver decides to call a
trap.

Also Fread() can "wrap" if it is done in the background and another
process decides to call the system in the meantime. If both calls go down
to the same BIOS function a mess is quite likely to occur.

--
Konrad M.Kokoszkiewicz
|mail: draco@mi.com.pl                  | Atari Falcon030/TT030/65XE |
|http://www.obta.uw.edu.pl/~draco/
|http://draco.atari.org

** Ea natura multitudinis est,
** aut servit humiliter, aut superbe dominatur (Liv. XXIV,25)
*************************************************************
** U pospolstwa normalne jest, ze albo sluzy ono unizenie,
** albo bezczelnie sie panoszy.