search for: huuuuuge

...ffset, because that's how all debug info is represented > in the PDB. So if there is no module, then there is no RVA (because the R > in RVA means relative, and what would it be relative to?). > > One idea to test this would be to create a DLL called jitted_code.dll, > give it a huuuuuge .text section (probably just a .asm file and use some > assembly directives to allocate a very large series of null bytes), and > then write your jit code into that area. This way you would not need to > modify the existing PDB you would only need to make a new PDB called > jitted_code...

...info is represented >>> in the PDB. So if there is no module, then there is no RVA (because the R >>> in RVA means relative, and what would it be relative to?). >>> >>> One idea to test this would be to create a DLL called jitted_code.dll, >>> give it a huuuuuge .text section (probably just a .asm file and use some >>> assembly directives to allocate a very large series of null bytes), and >>> then write your jit code into that area. This way you would not need to >>> modify the existing PDB you would only need to make a new PDB...

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