AW: AW: [wingide-users] Problems with wingdbstub.SuspendDebugPeter.Frey@haufe.de Peter.Frey at haufe.de
Tue, 8 Apr 2003 17:29:09 +0200
Hi Stephan, I found the cause of my startup performance problem: obviously too many breakpoints ... after invoking "Clear All Breakpoints" from the Breakpoint menu, the = startup time went from 5 to 6 minutes before down to approx 5 seconds.=20 Problem solved, thanks for your help. Peter N.B. - maybe as feature request: shouldnt the WingIDE not only show how = many modules loaded but also how many breakpoints in use? Semms to have a = heavy impact on debugging debug performance. -----Urspr=FCngliche Nachricht----- Von: Wing IDE Support [mailto:firstname.lastname@example.org]=20 Gesendet: Freitag, 4. April 2003 05:14 An: Peter.Frey@haufe.de Cc: email@example.com; firstname.lastname@example.org Betreff: Re: AW: [wingide-users] Problems with wingdbstub.SuspendDebug 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 = expect this to take. 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 = will 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 = should be able to see where it's getting stuck, at least as far as the network messages go. Thanks, - Stephan
Run by Mailman v 2.0.8
Copyright (c) 2000-2002, Archaeopteryx Software, Inc.