search for: jitted_code

...you want to. You'll need to > produce a jit_code.obj probably compiled from assembly that makes a section > named .jit and sets the flags to be executable (you can just copy the flags > from a normal .text section of some other program). Then link this file > together along with a jitted_code_main.obj which you compiled from a simple > source file with a DllMain function that does nothing. This would make > jitted_code.dll, then have your program link against jitted_code.lib. > > Right now you jit the code into some buffer that you created with > VirtualAlloc. If you do...

...and modules, this is what I m afraid of, doing all of this for nothing or almost.. Your idea looks good concerning the .text section in a separated dll, but will it be executable memory ? .text is where static strings go right ? When you say putting my jit in there, do you mean writing it when the jitted_code.dll is loaded in memory or on the .dll file directly before loading it ? In the first scenario I wonder if the section will be executable, in the second scenario I can’t do it because it would require perfect linking with the other code my jit points to.. Le mer. 23 janv. 2019 à 20:57, Zachary Tur...

That’s a good question, by default when emitting the object file I choose COFF but it embeds dwarf and not codeview in the end.. there probably is a way to do it or at least it must be implemented if not yet.. Lets imagine I manage to do that.. when you say there is nothing to do, I still must have a PDBFileBuilder to copy the codeview data inside the EXE PDB right ? I cannot insert them easily in