| ▲ | The GDB JIT Interface(bernsteinbear.com) | ||||||||||||||||
| 45 points by surprisetalk 5 days ago | 5 comments | |||||||||||||||||
| ▲ | amelius 42 minutes ago | parent | next [-] | ||||||||||||||||
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. | |||||||||||||||||
| ▲ | saagarjha 42 minutes ago | parent | prev | next [-] | ||||||||||||||||
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 | |||||||||||||||||
| ▲ | rurban 2 days ago | parent | prev [-] | ||||||||||||||||
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. | |||||||||||||||||
| |||||||||||||||||