[Pyobjc-dev] Best Practices for PyObjC debugging in Xcode?
Brought to you by:
ronaldoussoren
From: Daniel L. <da...@br...> - 2008-02-01 21:18:20
|
I would appreciate any sources of information anyone can point me to that offer some good best practices for PyObjC debugging using Xcode and gdb. While NSLog(), print(), and repr() suffice most of the time, it would be really nice to be able to get closer to source-level debugging with PyObjC like I can in plain-vanilla Python and wxPython with Komodo. I realize I cannot achieve that ideal, but I'd appreciate getting closer. For instance, I am using Apple Python 2.5.1 on Leopard right now: 1. would it help to build an unstripped MacPython framework build? I know PyObjC is unstripped if I build with py2app -A, but I'll have to dig down into Xcode to see how to arrange that for a debug target in Xcode 3. 2. Anyone know any good macros for gdb that help cut through and clear away all the stack detritus when gdb hits a break? Python is a great tool, but it leaves a fugly stack bt. 3. Right now, I break in main.m, set a bps on NSLog, having put NSLog calls in Python where I want to take a look at things--surely there are more clever folks out there than me. What do you do? 4. Any other useful tips, strategies, etc. I'll assemble things, write something up with examples, and put them in a Wiki once I work through whatever I can find. Google has returned a paucity of info on this which is why I am pinging the list. Daniel |