I have a client server application which uses a local file socket.
When i connect to the server part and then close the connection the
memory usage stays the same indicating that the resources aren't
freed. Other then this memory leak problem everything is working fine.
I assume, the memleak is not in the part of the code you've been sent,
but who knows. Let's exclude that case.
If I were you, I would change the server code to a short one, which
sends back a dummy simple "ok" or "fail" message (the simpler one), I
guess, the "..." part of your code is that place:
if (read(client_socket_fd, &length, sizeof (length)) > 0) {
.....
}
Then fire as many request as you can, and check the mem.
--
ern0.scene.plus4.amiga.code.muzak
Haben Sie Fragen?
--
To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
