Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
D

decentsmile

@decentsmile
About
Posts
1
Topics
0
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • CSocket::Create function has thrown exception
    D decentsmile

    Hi Guys, This same problem has driven me nuts but finally i fixed it and it is working. This is bug with MFC socket library that when inside a thread [other than main application thread], If we try to do something like CSocket socket; socket.Create(); It will throws an unhandled exception. I found an article on it See What Microsoft says about this that said something from Microsoft but that did not help me either. So here is a workaround i have found and i hope it can help some frustrated fellow like me. Inside thread, do this CSocket mySock; SOCKET sockethandle = socket(AF_INET, SOCK_STREAM, IPPROTO_TCP); mySock.m_hSocket= sockethandle; After that DO NOT call mySock.Create as it has been created already through assignment of socket handle. I am not sure if we can use mySock.Attach(sockethandle) as i did not try it yet. After that you can call Connect etc directly. When you are done using the socket, DO NOT call

    - rather call closesocket(mySock.m_hSocket); And that will free the socket object. If Attach works in above case then i guess we need to do Detach here when to free the socket. Good Luck Nauman Khan

    C / C++ / MFC help learning
  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups