My winsock server works without any string variables. If I add a string variable, the server compiles correctly but can't link or bind and the server fails and crashes. Without the string variable, everything runs fine. Yes, I have included this at the beginning: #include <winsock.h> #include <winsock2.h> #include <windows.h> #include <cstring> #include <string> #include <string.h> #include <iostream> #include <sstream> using namespace std; I am using dev-C++ compiler I would really like an answer!!! I have already spent 3 hours searching for it! [Edited by - hsdjjssjsdf on March 24, 2007 2:08:44 PM]

cut it down a bit :)


you can definitly remove #include <string.h>
in c++ you use
#include <cstring>
to get access to the old C string functions (strlen, strcat etc)
and #include <string> for C++ strings.

#include <string.h> is used in C not C++ (it works in C++ but since you are including cstring its redundant and likely to cause problems)

If you need more information, nothing is wrong with including both winsock files. nothing should be wrong with anything else because the server runs just fine with the exact inclusions, just without any string variables.

If I add only one line of a String variable, anyware, the server won't run. Without the string variable (Either initialied or not, whether at the begining or the end) the client and the server work just fine, can connect and send messages to each-other.

With the string variable, the server just doesn't start.
The client works just fine, with or without a string.
Also, they both use the windows API WinaMain function.

The client includes:

#include <sstream>
#include <iostream>
#include <string>
#include <cstring>

#include <sstream>
#include <iostream>
#include <string>
#include <cstring>

whoops pasted twice...;)
Anways, I would really like an answer!

Does this even have something to do with sockets?

If nobody connects, does the program stay up? Does it crash only when you're trying to send a string? If so, then you're probably not sending the characters of the string, instead trying to send the string object directly. That won't work; you have to use marshalling!

If it crashes when you start it, before any connection, then this is a linkage issue, and you'd be better helped in a tool-specific forum.

And, when posting these problems, you must post the following:

1) What is the exact error you're getting?
2) If this is at runtime, where does the debugger point, and what does the stack look like?
3) If you have inserted logging, or single-step through your program, what is the result?
4) If you say you're using a string, what is the code where that string is declared, and where it is used?

Despite multiple requests for this information, you have not posted it, which shows the forum that you're not really willing to actually read the help people are trying to offer. This means that less people will try to help you in the future, which is a bad thing. Please attempt to read the replies fully, think about what they mean, and then post a considered response.

Whether I use the string or not, the server still crashes. Here is more specific: Everything runs fine at first. I then add a string to test it, and I test it in several places like the beginning or end. I try styles stuch as "string variableString;" and "string stringVariable="";"and "string stringVariable="dd";" and "string stringVariable=string("Elephants")" and "string stringVariable="Him" in any place possible. EVery time it failed, even if I only included on string usage statement without even using it. The program crashes at the very bginning of runtime and returns a "SOCKET_ERROR" when both bind and link processses run. I get an error with the network linking process and the network process


And the program still runs, but wont use winsock becuse of these winsock errors thus making it hard to debug.

Example:

// Includes as before

API WinMain(Blah blah...)
{
string favouriteBook="Halo 2";
WSADATA WsaDat;
SOCKET Socket0;
SOCKADDR_IN SockAddr;


/// Blah blah...


//Error code

if(bind(Socket0, (SOCKADDR *)(&SockAddr), sizeof(SockAddr)) == SOCKET_ERROR)
{
*closeServer=TRUE;
MessageBox(NULL, "The networking linking process has failed\n\n\t", "Error", MB_OK|MB_ICONERROR);
} // I get this error




//Error code

if(listen(Socket0, 1) == SOCKET_ERROR)
{
*closeServer=TRUE;
MessageBox(NULL, "The networking listening process has failed\n\n\t", "Error", MB_OK|MB_ICONERROR);
} //tHIS TOO

// Extra message anylizing code
return 0;
}

Remember that this works exactly as it should but crashes for some dang reason when a simple string variable is declared, no matter how it is declared or initialize or used the positioned

Yes, the socket creation does work. It normally works and does not work ONLY when I declare a string variable

And, thank you very much for the support!! I appreciate it!!!

And and, how silly of me!!!!!!! I forgot the winsock code: 10049 so hold tight while I go see if I can see what that means unless you find it first

Looking up, I found WSAEADDRNOTAVAIL.

Here, my address and port code (I declare port before address)




SOCKADDR_IN SockAddr;
SockAddr.sin_port = htons((unsigned short)2765);
SockAddr.sin_family = AF_INET;
SockAddr.sin_addr.S_un.S_un_b.s_b1 = INADDR_ANY;

if(bind(Socket0, (SOCKADDR *)(&SockAddr), sizeof(SockAddr)) == SOCKET_ERROR)
{
//Blah blah get last error blah blah quit program blah blah show the error...uh....etc
}


The problem comes when the server uses the BIND function

Edit: OH and I use winsock version 2.0 in the server