Socket crashes on AccessViolationException when the peer side aborts (net2.0 beta2)
Hi,
I experienced a weird problem with socket on my machine. On my colleague's it works like a charm.
When I have socket, waiting for incomming data (after I called BeginReceive) and the peer side aborts - eg. I kill the telnet.exe who I used as a client, the socket throws AccessViolationException on unknown module.
The crash itself is in
> imon.dll!20b0cd39()
did anyone experienced something similar, or it's problem on my machine?
regards
georgem
[485 byte] By [
georgem] at [2007-12-17]
Could you tell us a little more info?
Do you have a call stack?
Can you send me your code that produces the issue?
Or even a dump file?
Unfortunately, I can't get this to repro on my side using a current build and the dump file you sent contains only a mini dump and is not enough information for me to debug this. Can you run under a debugger and catch the exception? Native debuggers can be found at:
http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx
You can then lauch your app, attach Windbg.exe to the process (comes with the above mentioned install package). Once Windbg.exe is attached to your application, cause the error to occur. You should see an AccessViolation message in Windbg.exe's command window. Run the command
.dump -f c:\SocketAccessViolation.dmp
Please send a zipped copy of that dmp file to Durga. Also, do you have access to a more recent build? If so, please run with a newer version and see if it still fails with the error.
. I sent it to the address, mr. Durgaprasad Gorti presents here on the pages dgorti@... If there's another address, I have no problem to send it there.