version40163
Premium Member
- Joined
- July 8, 2026
- Messages
- 2
- Reaction score
- 0
- Points
- 1
- Thread Author
- #1
Issue: The server process 2015Remote.exe crashes immediately after receiving client login data.
Root Cause:
The callback function pointer m_NotifyProc of the IOCPServer is not properly initialized when the listening port is activated.
In 2015RemoteDlg.cpp, after creating the IOCPServer instance, the message handling callback must be set:
cpp
// Current code (incorrect)
IOCPServer* pIOCPServer = new IOCPServer();
pIOCPServer->StartServer(nPort);
//
Missing: pIOCPServer->SetNotifyProc();
Verification Location:
server/2015Remote/2015RemoteDlg.cpp – inside the Activate() or ListenPort() function.
Fix Checklist:
Let me know if you also need a corresponding code fix example.
source code:Filebin | cewge98ffkfajvfy
The problem can be solved with USDT rewards, feel free to ask for more info. Who can fix this? Please contact: Abraham Reyna
Root Cause:
The callback function pointer m_NotifyProc of the IOCPServer is not properly initialized when the listening port is activated.
In 2015RemoteDlg.cpp, after creating the IOCPServer instance, the message handling callback must be set:
cpp
// Current code (incorrect)
IOCPServer* pIOCPServer = new IOCPServer();
pIOCPServer->StartServer(nPort);
//
Verification Location:
server/2015Remote/2015RemoteDlg.cpp – inside the Activate() or ListenPort() function.
Fix Checklist:
- Locate where the IOCPServer instance is created
- Ensure SetNotifyProc() is called before StartServer(), pointing to the MessageHandle function
- Ensure m_OfflineProc is also initialized (for client disconnection handling)
Let me know if you also need a corresponding code fix example.
source code:Filebin | cewge98ffkfajvfy
The problem can be solved with USDT rewards, feel free to ask for more info. Who can fix this? Please contact: Abraham Reyna