This was always too much work for not enough benefit. What I did in the case to debug into such cases, I constructed the C equivalent temporarily, compiled it on the fly also with -g, set the source to this file and could easily debug the function.
setheron 4 hours ago |
How do you know what the equivalent C is for the JIT assembly ?
rurban 4 hours ago |
Since I generate the asm part, generating the C part is easier.
I usually do just simple method JITs, which are C parts. Usually just calling an API method.
saagarjha an hour ago |
Anyone know how to actually enable this for, say, v8? I’ve debugged Chrome compiled code without symbols and it’s miserable and I’d really like to not have to do that
amelius 44 minutes ago |
Related, is there a way to get better backtraces for a Python program, in GDB?
I.e., showing the function names as they exist in Python, where relevant, and otherwise just the C names.