[wingide-users] embedded debugging problem

Adam Pletcher adam at volition-inc.com
Thu Nov 15 09:48:18 MST 2007


I've done that.  Without that it didn't even work the first time.

- Adam

> -----Original Message-----
> From: Wingware Support [mailto:support at wingware.com]
> Sent: Thursday, November 15, 2007 11:47 AM
> To: Adam Pletcher
> Cc: wingide-users at wingware.com
> Subject: Re: [wingide-users] embedded debugging problem
> 
> Adam Pletcher wrote:
> > I have an MFC app using embedded Python (2.5.1).  I have Wing
> listening
> > for remote debugging, and it brings up the debugger when my script
> > crashes, but only the first time it happens.  If I hit Stop it goes
> back
> > to listening, but fails to catch errors/breakpoints from additional
> runs
> > of that same script, or similar ones.
> >
> > If I restart my MFC app, however, it catches the first execution
> again.
> > Is there something in my app or Wing's config I need to do to get it
> to
> > catch subsequent debug events in that same app session?
> >
> > I searched the help/list archives but didn't come up with anything
on
> > this, but I'm a Wing IDE noob.
> > Suggestions appreciated.
> 
> You need to set kEmbedded=1 inside wingdbstub.py (it's 0 by default).
> If
> that doesn't help, please let us know.
> 
> --
> 
> Stephan Deibel
> Wingware | Python IDE
> Advancing Software Development
> 
> www.wingware.com



More information about the wingide-users mailing list