That would probably help with viewing of stacktraces and variable data,
but wouldn't opcodes still be needed to actually control stepping and
breakpoints in the app itself?
I guess it's possibly worth mentioning that I have a long-standing bounty
available for tasks that lead to viable debugging options; so far there
hasn't been much interest, though that's not surprising given that the
pool of possible developers is rather small :)
Bill
On Wed, 13 Jun 2012, Per Hedbor () @ Pike (-) developers forum wrote:
Actually, a much better solution would be to implement the JIT-debug
info generation supported by gdb (including variable mapping etc).
This should make it possible to simply debug using gdb, with symbols.
This can be done using a plugin with GDB 7.5+ (I think)
http://playingwithpointers.com/archives/633
or the old JIT registration API from GDB 7.0:
http://sourceware.org/gdb/current/onlinedocs/gdb/JIT-Interface.html
http://llvm.org/docs/DebuggingJITedCode.html
Doing it using a plugin seems to be the way to go, since that could
also handle things like priting of pike values, etc.
