Thanks, Donn... It turns out that versions of Wing older than about two
weeks (!) can't debug Python 2.4.1 - downloading a newer one fixed this.
I can now launch a debug session from within Wing against a full debug
build, then attach to the Chandler python_d process from within Visual
Studio and set breakpoints in wx and single-step, etc. I've got a new
problem, though: when using a full build from within Wing, Wing stops in
twisted's threads (without breakpoints!), gets confused, and kills the
target process - I'm still working on that.
...Bryan
Donn Denman wrote:
It works for me when I launch from the command line with the --wing
option. It will hit breakpoints set in wing. I just use the
"wingdebug" alias from the ShellScript wiki page.
I have NOT tried to set up a project to run debug directly from wing
though.
- Donn
On May 20, 2005, at 3:41 PM, Bryan Stearns wrote:
Has anyone done debugging from Wing on Windows with full debug builds
lately? (I'm unable to get it to run the python_d (or pythonw_d) that
I built.)
...Bryan
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
