I apologize for all these threads but this one has me truly stumped now...my program is going surprisingly well actually, until this point. Everything is compiling fine, but...
Whenever I put in this call, VS says I have unhandled exceptions in ntdll.dll. When I comment it out there are no exceptions at all.
recvfrom(sd, RecvBuf, BufLen, 0, (SOCKADDR *)&SenderAddr, &SenderAddrSize);
Yields:
Unhandled exception at 0x7c901230 (ntdll.dll) in bf2gui.exe: User breakpoint.
I don't know what it means by user breakpoint...I don't have any breakpoints in this program at all.
Then it points at the MessageBox function with a green arrow, or if I comment that out, it points to the line below it, activethreads--;. If both are commented it points to somewhere in a windows header file...
I have successfully used recv before but not recvfrom...I don't know why recvfrom isn't working...
Using Ethereal I can tell it is sending the query data I want it to, and the response seems correct. But I need to get that response in to a string without it failing somehow.
BTW, doing a char *buff=NULL;
buff=(char*)malloc(4096+1);
...
free(buff);
yields the same error in execution.
Whenever I put in this call, VS says I have unhandled exceptions in ntdll.dll. When I comment it out there are no exceptions at all.
recvfrom(sd, RecvBuf, BufLen, 0, (SOCKADDR *)&SenderAddr, &SenderAddrSize);
Yields:
Unhandled exception at 0x7c901230 (ntdll.dll) in bf2gui.exe: User breakpoint.
I don't know what it means by user breakpoint...I don't have any breakpoints in this program at all.
Then it points at the MessageBox function with a green arrow, or if I comment that out, it points to the line below it, activethreads--;. If both are commented it points to somewhere in a windows header file...
I have successfully used recv before but not recvfrom...I don't know why recvfrom isn't working...
Using Ethereal I can tell it is sending the query data I want it to, and the response seems correct. But I need to get that response in to a string without it failing somehow.
BTW, doing a char *buff=NULL;
buff=(char*)malloc(4096+1);
...
free(buff);
yields the same error in execution.