[wingide-users] Causing and Error with the Debug Probe Stops the Debugging

Clark Kogan kogan.clark at gmail.com
Fri Jun 4 10:01:25 MDT 2010

Sorry, that is my bad. It did not crash the debugger. It is just that the
red debugging highlight vanishes when you type an invalid command in the
debug probe.
- Clark

On Fri, Jun 4, 2010 at 7:17 AM, Wingware Support <support at wingware.com>wrote:

> Clark Kogan wrote:
>> Hi,
>> I am using wingide professional. If I am trying to debug a program, and
>> during the debugging process, I type an invalid command in the Debug Probe,
>> then the debugging stops, and I have to run the program again. Is there some
>> way allow invalid commands in the Debug Probe without exiting the debug
>> process?
> Generally an invalid command should just print the traceback and not exit.
>  If the command actually crashes the debug process that is of course another
> story.  Can you check whether this command executed at that point in the
> code (by adding it to your sources) would also crash the process outside of
> Wing's debugger?  If it does not, please let us know more about the command
> that is causing this.
> Thanks,
> --
> Stephan Deibel
> Wingware | Python IDE
> Advancing Software Development
> www.wingware.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: /pipermail/wingide-users/attachments/20100604/a283dd71/attachment.html

More information about the wingide-users mailing list