Frank Naumann wrote:
Hello!Don't know if it help: PROCESS "KRONOS" KILLED: MEMORY VIOLATION. Type: private PC: 01D098EC Addr: 01D8D66E BP: 01CA8000If it's gcc compiled (with debug info) you can calculate the source line of the crash from the PC.Yes it is, how can I do? I have no gdb (I can download it if need).gdb is not needed (with gdb you can do source level debugging).Compile a KRONOS version with debug (option -g). Then let the version run, remember the crashing PC and the BP. Now calculate PC - BP - 0x100 and enter this value into addr2line -e kronos.prg. If the PC is a useful PC (e.g. the PC is inside the program AND belongs to code that is compiled with debug info) addr2line print the corresponding source line.
HelloJust to said (I'm still on hollyday's) that I have test Kronos under the buggy version of winaranym with MMU (MMU work but Mint crash when an exception occur with MMU (Aranym known problem not Mint problem)). Because I can't launch XAAES with this version I have done a port of myaes (very alpha at this stage), and Kronos can work, but it need to change flag for kronos.app to MX_GLOBAL. With this, desk is avaible and I have no crash with openGL test. I know exactly what is problem with MyAeS and I'm working to solve it soon. I think it should be possible to work in private mode.
Olivier