On 06/28/2010 04:34 PM, Yaroslav Halchenko wrote: > AFAIK: > > - regular python build symbols files are useful for anyone willing to > troubleshoot the problem which is not too complicated and he wouldn't > need to explore the state of Python at the troublesome moment. > > - _d* files for python*-dbg are extremely useful if someone needs to > triage the problem which cannot be easily comprehended by just looking > at the stack of compiled extension. Then various tricks (Python's > ./Misc/gdbinit, or new way ./Tools/gdb/libpython.py) allow much easier > bug/problem triage in Python extensions using debug build of Python
also - and that is the much more important imho part for pyside - if you want to run something else in the debug interpreter which uses pyside, you need the _d build of pyside, too. -- Bernd Zeimetz Debian GNU/Linux Developer http://bzed.de http://www.debian.org GPG Fingerprints: 06C8 C9A2 EAAD E37E 5B2C BE93 067A AD04 C93B FF79 ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c2b5662.5080...@bzed.de
