[Dev] Wing IDE debugging problem

[Ken Krugler]

Hi Donn,

>Tell us more about how your Wing fails.  Does it launch?  Are you 
>having trouble debugging?
>
>Many of us run on Macs, and although we have seen some problems, it 
>doesn't simply fail.

Below is the email I sent to Wing IDE support:

======================================================================
I'm running Mac OS 10.3.6, Wing IDE 2.0.0, on a G4 PowerBook.

I set up my project using the same settings that John Anderson has 
for a working project, other than debug vs. release (I'm targeting a 
debug build of Chandler, while he's using a release build)

The problem is that when I try to debug the Chandler project, I never 
hit a breakpoint I set in the first file, and debugging never seems 
to really start up.

When I click the Debug button, the status panel says "Debugger: 
Listening for back-connection". In about four seconds this changes to 
"Debugger: No debug process / not listening for connections". A few 
seconds after that, the message goes away, and I'm back to where I 
started.

In the Python Shell pane, it says "Cannot execute: waiting for 
sandbox process to restart". So it seems as though my Python 
interpreter isn't available.

But I can run the project from the command line, using the same 
Python interpreter that I think I've configured with Wing IDE. This 
is version 2.3, which is included inside of the Chandler project.

Not that this matters, but I can run/debug Python programs using the 
default pre-installed Python that came with Mac OS 10.3 (Python 2.3), 
using MacPython.
======================================================================

-- Ken

>On Dec 6, 2004, at 3:37 PM, Ken Krugler wrote:
>
>>Hi all,
>>
>>I was having problems getting the debugger in Wing 2.0.0 to work 
>>with Chandler. This is on Mac OS 10.3.6. Based on some logged 
>>output that I sent them, Wing IDE Support said:
>>
>>>Thanks.  I'm guessing you ended up building Python 2.3.3 with the
>>>--with-pydebug configuration option and we omitted support for
>>>that in Wing 2.0.0 on OS X (by accident, as it turns out).
>>>
>>>If I'm right about that, you can either build the debugger against your
>>>copy of Python (I can provide details if you choose to do this), change to
>>>building w/o --with-pydebug, or wait until Wing 2.0.1 is released (which
>>>will re-add the support for this compilation variant on OS X).
>>
>>Does this make sense? I'm curious as to why John's configuration 
>>works, and mine doesn't. Though he was running against a release 
>>build of Chandler, and I was using the debug build...could that 
>>have altered the --with-pydebug setting?
>>
>>Thanks,
>>
>>-- Ken


-- 
Ken Krugler
TransPac Software, Inc.
<http://www.transpac.com>
+1 530-470-9200