AW: [wingide-users] Problems with wingdbstub.SuspendDebugWing IDE Support support at wingide.com
Thu, 3 Apr 2003 22:13:57 -0500 (EST)
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 On Thu, 3 Apr 2003 Peter.Frey@haufe.de wrote: > Hi Stephan, >=20 > it works. But unfortunately it did not solve my startup performance probl= em. > I did implement your proposal as follows: >=20 > def cmsquery(args =3D None): > if not args: > args =3D sys.argv >=20 > if WINGDEBUG: > print "%s loading Wing Debugger ..." % now_time() > import wingdbstub > print "%s Wing Debugger loaded, parsing command line options ..."= % > now_time() > else: > print "%s parsing command line options ..." % now_time() >=20 > options =3D Options() #... breakpoint here ... >=20 > if __name__ =3D=3D '__main__': > cmsquery() >=20 >=20 > when starting now my script I get the display of "Debugger: Program runni= ng > (694 modules loaded)" very quickly > (approx. 5 seconds) >=20 > but it looks now like the "import wingdbstub" takes > 5 minutes (before i= t > was "import Zope" that took that long). > the output of my script looks now like >=20 > freyp@mycomputer:~/EPcvs/HRS/Prod/HaufeCMSScripts> sh start_query.sh > 22:52:04 QueryTest started > 22:52:04 starting up Zope environment ... > 22:52:08 loading HaufeCMS ... > 22:52:09 loading Wing Debugger ... > 22:57:35 Wing Debugger loaded, parsing command line options ... >=20 > Is there anything else I could do to speed this up? >=20 > Peter >=20 > -----Urspr=FCngliche Nachricht----- > Von: Wing IDE Support [mailto:email@example.com]=20 > Gesendet: Donnerstag, 3. April 2003 22:19 > An: Peter.Frey@haufe.de > Cc: firstname.lastname@example.org > Betreff: Re: [wingide-users] Problems with wingdbstub.SuspendDebug >=20 >=20 > Hi, >=20 > The API will only work if you're launching the debug process from outside= of > Wing. If you debug from within Wing, the debugger is already going by th= e > time you reach the import of wingdbstub, so the module does nothing and > doesn't set up the debugger API. When you ran from the command shell it > also didn't work because there's a bug in SuspendDebug that needs=20 > fixing (oops, thanks for pointing it out!). >=20 > However, you probably don't need to use the API anyway. At this point th= is > is really only there for very unusual debugging scenarios. >=20 > Try removing your calls to the API and placing the import of wingdbstub > where you currently have the ResumeDebug call. This will delay starting > debug until that line is reached. >=20 > If you want to launch the process from the IDE, use the Execute items in = the > Run menu instead. This runs things outside of the debugger and lets > wingdbstub do its work when it is imported. >=20 > If you do need .wingdebugpw, it's in ~/.wingide on Linux/Unix, and inside > profiles/[username] in your Wing installation on Win32. However, if both= =20 > processes run as the same user then the debugger looks up the file=20 > automatically. >=20 > Hope that helps... if not, please let us know. >=20 > Thanks, >=20 > Stephan Deibel >=20 > -- > Wing IDE for Python > Archaeopteryx Software, Inc > Take Flight! >=20 > www.wingide.com >=20
Run by Mailman v 2.0.8
Copyright (c) 2000-2002, Archaeopteryx Software, Inc.