[wingide-users] Tricky embedded application -- resuming debugger

reckoner reckoner at gmail.com
Mon May 24 14:02:07 MDT 2010


John:

This seems to work! I can't tell you how much easier this makes 
debugging this application for me.

Thanks again.

On 5/24/2010 9:32 AM, John Ehresman wrote:
> On 5/24/10 12:19 PM, reckoner wrote:
>> Then, finally, my question is whether or not I'm doing this correctly. I
>> have tried setting kEmbedded in the wingdbstub file, but that doesn't
>> seem to help. I would prefer to hit the breakpoints in other modules
>> besides the initialization module without having to "Step" my way
>> through to them.
>
> Could you try using the attached wingdbstub.py ? It fixes how kEmbedded
> is handled. Also, are you using the StartDebug() debugger api function?
> If so, you need to specify autoquit=False in each call. This is a flaw
> in the api in Wing 3.x, which is being fixed in Wing 4.x.
>
> Thanks,
>
> John


More information about the wingide-users mailing list