Arno Garrels wrote:
> Wilfried Mestdagh wrote:
>> Hello Arno,
>>
>>> procedure PatchINT3;
>>
>> This procedure works great. But something is strange. If I run this
>> in a separate application then it does not work. However as far as I
>> know a DLL is loaded only once in memory.
>> So then it sh
Wilfried Mestdagh wrote:
> Hello Arno,
>
>> procedure PatchINT3;
>
> This procedure works great. But something is strange. If I run this
> in a separate application then it does not work. However as far as I
> know a DLL is loaded only once in memory.
> So then it should work also
> if I run thi
Hello Arno,
> procedure PatchINT3;
This procedure works great. But something is strange. If I run this in a
separate application then it does not work. However as far as I know a
DLL is loaded only once in memory. So then it should work also if I run
this in a separate app and let the other appli
Wilfried Mestdagh wrote:
> The only strange thing is, that I never had that problem (win xp sp3,
> D7), but it could be by a recent upgrade service pack maibe...
Maybe? I run the last online update a couple of weeks ago.
--
Arno Garrels
--
To unsubscribe or change your settings for TWSocket ma
Hello Arno,
This is interesting. If I see it clear you change the int 3 with a nop
instruction.
The only strange thing is, that I never had that problem (win xp sp3,
D7), but it could be by a recent upgrade service pack maibe...
---
Rgds, Wilfried [TeamICS]
http://www.overbyte.be/eng/overbyte/te
Hoby Smith wrote:
> Anyway, if that is the case, there is nothing you can do but just
> live with it or upgrade the OS. :)
Actually you can, see OverbyteIcsNtlmSsp.pas:
{ Get rid of some ntdll.DbgBreakPoints M$ forgot to remove from their DLLs }
{ popping up the CPU window. Written by Francois
Korotky.
- Original Message -
From: "Wilfried Mestdagh"
To: "ICS support mailing"
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
> debugge
> Wilfried said...
> NTdll.DBGBreakPoint
> int 3
> ret
What OS and version? I can't remember exactly what version it was, but I
seem to recall that, quite some time ago, MS accidentally released a WinSock
(or some related DLL) build into production that still had a hard break in
it from o
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://w
