Jo Even Skarstein a écrit :
OL wrote:As I notice it crash desktop with AV protocol but this is only a problem with memory protection, and a lot of softwares do the same.I think the problem is more serious than that. On my Milan I have to reset after exiting zView. zView is killed due to a memory violation, but I don't think it's related to the AV-protocol. XaAES doesn't respond to the mouse or keyboard afterwards. To be honest I'm not a fan of all these module-loaders. GEM-View, PARX, Smurf, LDG... They all seem to cause various problems for me.
Just a word to said my own program use all dynamic libs (LDG) and as my know they work fine (Kronos, MyAES, Inshape3...).
I notice in protected mode that Zview crash too under MyAES because I never receive appl_exit() but I not notice any trouble for MyAES in this case that continue to work perfectly. (I have only test with Aranym MMU and Mint with most protected )
Yes it look in appl_write() call AV messages and the application sending AV message copy itself in a share buffer the message in the AES.If AES intercept this message and and clean the protocol (probably itHow does MyAES intercept this? Does it check all pointers passed in AV-messages?
should be but it is not) Zview work for me perfectly in protected mode except when it quit but it crash alone.This is probably the same problem as I have.
Yes and I'm happy because it looks not a specific problem with MyAES.Someone report it crash in ldg_unload() this is strange, I have to look in this, but perhaps there is a corruption memory by lib itself or a stack overflow somewhere.
Olivier
Jo Even