2 okt 2011 kl. 18:00 skrev Adam Kłobukowski:
If some other application isn't configured correctly (i.e. the flags in the header of the executable), the kernel may kill Thing because it's trying to access the memory of that application (which is required by some GEM protocols). Since a lot of code has been developed using that bad excuse for an OS called MagiC (which lacks memory protection), it's not entirely uncommon that applications aren't setup correctly. IIRC there's a good doc about that in the freemint sources… somewhere.
IIRC Thing is smart enough to avoid that.
Thing is. Other applications are not, and that's the point. If Thing access the memory of another application (which is the case), and that application didn't declare that memory as global (either through the executable flags, or explicitly while allocating memory), the kernel will kill Thing for it. There's nothing Thing can do to prevent that.