I wonder if there is a way to make this situation easier? Perhaps for
debug builds, we can store some debug information in the frame object,
e.g. utf8 encoding of the filename and function?
I'd like to stress Benjamin's recommendation. Dave Malcolm's gdb
extensions (requires gdb with Python
Cc: python-dev@python.org
Efni: Re: [Python-Dev] Pep 393 and debugging
I wonder if there is a way to make this situation easier? Perhaps for
debug builds, we can store some debug information in the frame object,
e.g. utf8 encoding of the filename and function?
I'd like to stress Benjamin's
I just had my first fun with Pep 393 strings and debuggers. Trying to debug a
deadlocked python program, I'm trying to figure out the callstack of the thread
in the debugger.
I ended up with something like:
(char*)((PyASCIIObject*)(tstate-frame-f_code-co_filename))[1]
while previously,
2012/4/6 Kristján Valur Jónsson krist...@ccpgames.com:
I wonder if there is a way to make this situation easier? Perhaps for
debug builds, we can store some debug information in the frame object,
e.g. utf8 encoding of the filename and function?
Have you tried using the cpython gdb plugin? It
