AW: AW: [wingide-users] Problems with wingdbstub.SuspendDebug

Hi,

Glad to hear you found the problem.  We'll have to look at why many
breakpoints slow it down so much; it really shouldn't degrade performance
more than a tiny bit!

Thanks,

- Stephan

On Tue, 8 Apr 2003 Peter.Frey@haufe.de wrote:

> Hi Stephan,
>=20
> I found the cause of my startup performance problem: obviously too many
> breakpoints ...
> after invoking "Clear All Breakpoints" from the Breakpoint menu, the star=
tup
> time  went from 5 to 6 minutes before
> down to approx 5 seconds.=20
>=20
> Problem solved, thanks for your help.
>=20
> Peter
>=20
> N.B. - maybe as feature request: shouldnt the WingIDE not only show how m=
any
> modules loaded but also how many breakpoints in use? Semms to have a heav=
y
> impact on debugging debug performance.
>=20
> -----Urspr=FCngliche Nachricht-----
> Von: Wing IDE Support [mailto:support@wingide.com]=20
> Gesendet: Freitag, 4. April 2003 05:14
> An: Peter.Frey@haufe.de
> Cc: support@wingide.com; wingide-users@wingide.com
> Betreff: Re: AW: [wingide-users] Problems with wingdbstub.SuspendDebug
>=20
>=20
> This is odd since by the time Wing says "Debugger: Program running (N
> modules loaded)" it has already transferred the largest bulk of info that
> gets sent at debug startup, so I'm not sure what else it's doing.  Also,
> even on a pretty slow machine 5 minutes is a hugely more than I would exp=
ect
> this to take.
>=20
> Try running with kSilent=3D0 in wingdbstub.py and possibly also with the
> --verbose switch on the command line when you start Wing.  The former wil=
l
> output verbose debugger-side info when you 'sh start_query.sh' and the
> latter will show some IDE-side messages.  All have time stamps so we shou=
ld
> be able to see where it's getting stuck, at least as far as the network
> messages go.
>=20
> Thanks,
>=20
> - Stephan
>=20