https://bugs.kde.org/show_bug.cgi?id=492835
--- Comment #2 from timona...@gmail.com --- To prevent any confusion, this issue is only about getting information about jit frames out of the jit compiler and into valgrind for use in callgrind/cachegrind and whatever else shows function names and stack traces. Actually just running code in jitted frames works fine, and there is the VALGRIND_DISCARD_TRANSLATIONS client request, but it is only necessary when valgrind has created a translation of code in a memory area, and the program changes the code - "self modifying code". Making sure that the translation valgrind has for the code in a given memory range is orthogonal to what I created this issue for. The JIT in MoarVM never writes to the memory ranges where it emitted jitted code after it has been "committed", which in our case means calling mprotect with "read and execute" on it. There is also an old patch here in the bug tracker for letting valgrind read ELF structures from memory instead of only from disk: #319237 (https://bugs.kde.org/show_bug.cgi?id=319237). This could help with this feature request in a pinch, but as I mentioned in the original description, having to create a full ELF structure is tedious, even if you don't have to write it to disk and load it from a file each time. -- You are receiving this mail because: You are watching all bug changes.
