- edited description
DUnitX - Crash when running under test insight.
Issue #14
closed
I'm seeing a crash when trying to run my DUnitX test project, seems like it was a port issue, as soon as I changed the default port range it started working fine.
exception class : EIdWinsockStubError
exception message : Error on call to Winsock2 library function shutdown: Either the application has not called WSAStartup, or WSAStartup failed.
main thread ($2438):
0298aefe IndySystem210.bpl IdWinsock2 6006 FixupStub
0298b7e2 IndySystem210.bpl IdWinsock2 6166 Stub_shutdown
0299632e IndySystem210.bpl IdStackWindows 1616 TIdStackWindows.WSShutdown
02996f86 IndySystem210.bpl IdStackWindows 2001 TIdStackWindows.Disconnect
02ca5c3e IndyCore210.bpl IdSocketHandle 273 TIdSocketHandle.Disconnect
02ca5c79 IndyCore210.bpl IdSocketHandle 284 TIdSocketHandle.CloseSocket
02cb6b9a IndyCore210.bpl IdIOHandlerSocket 248 TIdIOHandlerSocket.Close
02cb9b60 IndyCore210.bpl IdTCPConnection 516 TIdTCPConnection.Destroy
02b0a933 IndyProtocols210.bpl IdHTTP 723 TIdCustomHTTP.Destroy
5005f108 rtl210.bpl System 15718 TObject.Free
0051c54d FinalBuilderTest.exe TestInsight.Client 374 TTestInsightRestClient.Destroy
50066bf6 rtl210.bpl System 37030 TInterfacedObject._Release
50066a9c rtl210.bpl System 36046 @IntfClear
500636d0 rtl210.bpl System 31435 @FinalizeArray
500635c0 rtl210.bpl System 31136 @FinalizeRecord
5005f17e rtl210.bpl System 15855 TObject.CleanupInstance
5005eff9 rtl210.bpl System 15649 TObject.FreeInstance
50066bf6 rtl210.bpl System 37030 TInterfacedObject._Release
50066a9c rtl210.bpl System 36046 @IntfClear
0050ee5a FinalBuilderTest.exe DUnitX.TestFramework 865 Finalization
50060a1a rtl210.bpl System 22093 FinalizeUnits
0046c678 FinalBuilderTest.exe madExcept InterceptFinalizeUnits
0046c687 FinalBuilderTest.exe madExcept InterceptHalt0FinalizeUnits
50061094 rtl210.bpl System 23473 @Halt0
006cdd36 FinalBuilderTest.exe FinalBuilderTest 158 initialization
76933388 kernel32.dll BaseThreadInitThunk
Comments (3)
-
repo owner -
repo owner -
assigned issue to
In the next build an option in the http listener has been changed that sometimes caused problems with sockets reuse. Please report if you see that problem again.
-
assigned issue to
-
repo owner - changed status to closed
- Log in to comment
Which port was it trying to connect to when this error occured? Was it the port the plugin was listening on?