[wingide-users] follow up to : Problem attaching to ZopeRobert Rottermann firstname.lastname@example.org
Sun, 13 May 2001 21:43:03 +0200
Hi there, here some more facts I discovered: When Zope is started Wing status changes to Debugger: Programm running However as soon an breakpoint is hit the following output is created in the dosbox from where I started Zope: 2001-05-13T19:32:36 ERROR(200) ZServer uncaptured python exception, closing channel <zhttp_channel connected 127.0.0.1:1870 at 19e9dd8 channel#: 30 requests:2> (socket.error:(10054, 'winsock error') [K:\Programme\zope\ZServer\medusa\asynchat.py|initiate_send|211] [K:\Programme\zope\ZServer\medusa\http_server.py|send|399] [K:\Programme\zope\ZServer\medusa\asyncore.py|send|282]) Thanks for your time Robert ----- Original Message ----- From: Robert Rottermann To: email@example.com Sent: Sunday, May 13, 2001 9:26 PM Subject: Problem attaching to Zope Hi there, I today downloaded the 1.1b5 Trial version of Wing. Performing the test with the wingTest product works as detailled in the tutorial. However I can not attach to Zope or have a breakpoint hit from Zope. I have z2.py adapted as outlined in the setup. Wing says Debugger: Reddy and listening When I try to attach to a running process I get the following error: Debugging stopped Unexpetedly: Runtime failure details: Exception: socket error Value=(10054, 'winsock error') Traceback: File "/src/ide/bin\1.5.2\src\debug\server\netproxy.pyo", line 1072 in _SendCommand File "/src/ide/bin\1.5.2\opensource\schannel\securechannel.pyo", line 384 in ReceivePacket .. line 501 in __RedRawPacket .. line 528 in __InternalReadRawPacket File "<string>", line 1, in recv My Environment: Windows 2000 Zope 3.3.2 Your help would be very much appreciated. Robert
Run by Mailman v 2.0.8
Copyright (c) 2000-2002, Archaeopteryx Software, Inc.