search for: af062585affb7cd16bab9867b706ea460

...Programs running under the JIT are > free to make any memory operation or function call that the enclosing > program could, even _exit(). You can try to restrict function calls by > removing the name resolution: > > > > http://llvm.org/doxygen/classllvm_1_1ExecutionEngine.html#af062585affb7cd16bab9867b706ea460 > > and/or installing your own (see InstallLazyFunctionCreator), but ultimately > they're the same process/task from the point of view of the operating system > and there's no "llvm security model" or anything like that. > > If you're very determined, you cou...

...is not a secure VM like Java. Programs running under the JIT are free to make any memory operation or function call that the enclosing program could, even _exit(). You can try to restrict function calls by removing the name resolution: http://llvm.org/doxygen/classllvm_1_1ExecutionEngine.html#af062585affb7cd16bab9867b706ea460 and/or installing your own (see InstallLazyFunctionCreator), but ultimately they're the same process/task from the point of view of the operating system and there's no "llvm security model" or anything like that. If you're very determined, you could create an LLVM IR trans...

Hi, I'm doing some tests concerning the embedding of LLVM and clan in my application. Now I stumbled across the following ... which disturbs me. If the jitted program crashes, like e.g. if it contains an assert(0==1) or calls an external function which cannot be resolved, the hosting app goes down as well. There seems no error catch. Can this anyhow be circumvented? -Frank

...cure VM like Java. Programs running under the JIT are free to make any memory operation or function call that the enclosing program could, even _exit(). You can try to restrict function calls by removing the name resolution: > > > http://llvm.org/doxygen/classllvm_1_1ExecutionEngine.html#af062585affb7cd16bab9867b706ea460 > > and/or installing your own (see InstallLazyFunctionCreator), but ultimately they're the same process/task from the point of view of the operating system and there's no "llvm security model" or anything like that. > > If you're very determined, you could creat...

...JIT are >> free to make any memory operation or function call that the enclosing >> program could, even _exit(). You can try to restrict function calls by >> removing the name resolution: >> >> >> >> http://llvm.org/doxygen/classllvm_1_1ExecutionEngine.html#af062585affb7cd16bab9867b706ea460 >> >> and/or installing your own (see InstallLazyFunctionCreator), but >> ultimately they're the same process/task from the point of view of the >> operating system and there's no "llvm security model" or anything like that. >> >> If you're...