[Dev] Wing IDE debugging problem
donn at osafoundation.org
Mon Dec 6 18:27:14 PST 2004
Thanks for the details. I've had similar problems on the Mac, and the
Wing folks might be right that the python build/version is the problem.
I normally run Chandler from the command line on Mac, because it's so
much faster. You can also pass a -wing parameter to bring up wing and
debug that process when it hits a breakpoint. I just tried to do this
with the release build of chandler and I got an error that makes sense:
Error: Cannot run a debug process with optimized python because
Error: this omits necessary debug information from byte code.
However I can do the same thing on the PC without this problem. I
don't know why the two platforms are different in this regard.
Next, I tried to run the debug version of Chandler from the command
line and got a different error, that appears to be related to our
recent upgrade to wxWidgets 2.5.3.
So it looks like we can't debug on the Mac right now. Maybe someone
more familiar with the build can help us figure out what's going wrong.
On Dec 6, 2004, at 4:36 PM, Ken Krugler wrote:
> 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
> 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
> 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
>>>> 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
>>>> 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?
>>> -- Ken
> Ken Krugler
> TransPac Software, Inc.
> +1 530-470-9200
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> Open Source Applications Foundation "Dev" mailing list
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 4013 bytes
Desc: not available
Url : http://lists.osafoundation.org/pipermail/dev/attachments/20041206/f744449a/attachment.bin
More information about the Dev