[Python-Dev] Pep 393 and debugging (original) (raw)
Kristján Valur Jónsson kristjan at ccpgames.com
Sun Apr 8 02:49:09 CEST 2012
- Previous message: [Python-Dev] Pep 393 and debugging
- Next message: [Python-Dev] Summary of Python tracker Issues
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Thanks, _PyObject_Dump sounds like just the ticket. Most of the time, the VS2010 debugger can just run functions willie nillie and thing should simply work.
Frá: "Martin v. Löwis" [martin at v.loewis.de] Sent: 7. apríl 2012 09:08 To: Kristján Valur Jónsson Cc: python-dev at 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 recommendation. Dave Malcolm's gdb extensions (requires gdb with Python support) are really powerful; they will automatically render PyObject* by displaying the actual logical value (and not just for strings).
Failing that, I use _PyObject_Dump to display strings; this requires a debugger that can call functions in the debuggee (like gdb).
Regards, Martin
- Previous message: [Python-Dev] Pep 393 and debugging
- Next message: [Python-Dev] Summary of Python tracker Issues
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]