Hi, Wilfried, If my guess is correct and I'm not mistaken the issue is not specific to TWSocket, but to the way how Borland and MS live together. I've stumbled upon it several years ago in an application without ICS components (WinXP + BCB5).
I don't remember exactly what solution was applied that time, but what I've found just now - http://cc.codegear.com/Item.aspx?id=15804. Please check if it helps in your case. Some clarifications may be found in the Net, for example - http://www.delphiturkiye.com/forum/viewtopic.php?f=19&t=11275 Best wishes, Stanislav Korotky. ----- Original Message ----- From: "Wilfried Mestdagh" <wilfr...@mestdagh.biz> To: "ICS support mailing" <twsocket@elists.org> Sent: Wednesday, January 21, 2009 7:28 PM Subject: [twsocket] breakpoint in NTDll > Hello, > > I run a certain application using TWSocket, and when I run it in the > debugger, then every time when a re Connect is happening (if no server > available) the debugger stops at a hardcoded break: > > NTdll.DBGBreakPoint > int 3 > ret > > any idea how this can happen ? > > -- > Rgds, Wilfried > http://www.mestdagh.biz > > -- > To unsubscribe or change your settings for TWSocket mailing list > please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket > Visit our website at http://www.overbyte.be > -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
