Winsock 2 LSP Problems.

NTFSD
1

Hi,

I am having problems with creating a winsock LSP. I am going of the LSP
example that’s in the Platform SDK. I can get the ws2_32.dll to call
WSPStartup but when debbuging an application that uses winsock they fall
over with the following error:-

(558.55c): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
eax=00000001 ebx=00000000 ecx=00000202 edx=00dfd740 esi=0013eb08
edi=00000202
eip=77e777f8 esp=0013ee64 ebp=0019ae50 iopl=0 nv up ei pl zr na
po nc
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000
efl=00010246
kernel32!InterlockedIncrement+9:
77e777f8 f00fc101 lock xadd [ecx],eax
ds:0023:00000202=???

Anybody got any ideas on why it’s doing this?

This email has been scanned for all viruses by the MessageLabs SkyScan
service. For more information on a proactive anti-virus service working
around the clock, around the globe, visit http://www.messagelabs.com

2

An access violation is usualy due to an erratic pointer. You dont give us
enough information to point the exact mistake, try to always use appropiate
symbols for a clear stack backtrace.

Ciao

----- Original Message -----
From: “Ceri Coburn”
To: “File Systems Developers”
Sent: Thursday, August 15, 2002 2:19 PM
Subject: [ntfsd] Winsock 2 LSP Problems.

Hi,

I am having problems with creating a winsock LSP. I am going of the LSP
example that’s in the Platform SDK. I can get the ws2_32.dll to call
WSPStartup but when debbuging an application that uses winsock they fall
over with the following error:-

(558.55c): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
eax=00000001 ebx=00000000 ecx=00000202 edx=00dfd740 esi=0013eb08
edi=00000202
eip=77e777f8 esp=0013ee64 ebp=0019ae50 iopl=0 nv up ei pl zr na
po nc
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000
efl=00010246
kernel32!InterlockedIncrement+9:
77e777f8 f00fc101 lock xadd [ecx],eax
ds:0023:00000202=???

Anybody got any ideas on why it’s doing this?


This email has been scanned for all viruses by the MessageLabs SkyScan
service. For more information on a proactive anti-virus service working
around the clock, around the globe, visit http://www.messagelabs.com

—
You are currently subscribed to ntfsd as: xxxxx@rdsor.ro
To unsubscribe send a blank email to %%email.unsub%%

3

You are most likely passing bad arg to InterLockedIn*().

[ecx] is trying to access 0x202.

-prokash

-----Original Message-----
From: Ceri Coburn [mailto:xxxxx@first4internet.co.uk]
Sent: Thursday, August 15, 2002 3:19 AM
To: File Systems Developers
Subject: [ntfsd] Winsock 2 LSP Problems.

Hi,

I am having problems with creating a winsock LSP. I am going of the LSP
example that’s in the Platform SDK. I can get the ws2_32.dll to call
WSPStartup but when debbuging an application that uses winsock they fall
over with the following error:-

(558.55c): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
eax=00000001 ebx=00000000 ecx=00000202 edx=00dfd740 esi=0013eb08
edi=00000202
eip=77e777f8 esp=0013ee64 ebp=0019ae50 iopl=0 nv up ei pl zr na
po nc
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000
efl=00010246
kernel32!InterlockedIncrement+9:
77e777f8 f00fc101 lock xadd [ecx],eax
ds:0023:00000202=???

Anybody got any ideas on why it’s doing this?

This email has been scanned for all viruses by the MessageLabs SkyScan
service. For more information on a proactive anti-virus service working
around the clock, around the globe, visit http://www.messagelabs.com

You are currently subscribed to ntfsd as: xxxxx@zonelabs.com
To unsubscribe send a blank email to %%email.unsub%%