[Pythonmac-SIG] Debugging a MacPython Carbon module from CW9?

[Jay Koutavas]

Hi folks.

The product I'm developing for requires I do some implementation 
using MacPython 2.2.3 running on Carbon (it's got the 
GUSI2-for-Carbon package). (Not on 2.3 because the customer's 
extensive crossplatform python code base is 2.2 dependent) (and not 
native OS X Python cuz it has to run on Mac OS 9 too.)

The client's application embeds python via PythonCoreCarbon and 
through various .py files imports a few dozen modules of their 
devising, some are C++-based shared libraries. There's a bug in one 
of these shared libraries, and for the life of me, I'm not getting my 
breakpoint to stick in the shared library so I can have a look. I've 
added the shared library to 'Other Executables' in the main app's 
settings, which works great for debugging the PythonCoreCarbon shared 
library, but doesn't do much of anything for debugging module shared 
libs. Of course I have the module's shared library project file open 
at launch/debug time. But alas, no joy.

Anyone dealing with such a scene out there and are willing to throw 
this old dog a bone on the finer points of setting up a debug 
environment for Python module shared libs? :)

I'm using CodeWarrior 9.2(?) -- not sure if its 9.1 or 9.2, but the 
IDE's About Box says build #1429.

Thanks in advance,

/jay

-- 
'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
   Jay Koutavas                         mailto:jay at heynow.com
   Heynow Software                      http://www.heynow.com
   Windham, New Hampshire, USA
'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''