Instead of read each line in details, have a try for valgrind. -Sam On Tue, Jan 12, 2010 at 4:37 AM, Glynn Clements <glynn@xxxxxxxxxxxxxxxxxx> wrote: > > Uğur ATA wrote: > >> 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. >> Messeages are sent and received. After each message is sent/received >> rss indicator in the ps command increases with different amounts for >> each different message. When the rss reaches around 64MB the program >> stops working and freezes. Then it needs to be restarted. >> I couldn't find a solution to this problem anywhere on the web so >> thanks in advance if someone could be of help. >> Below is the result of uname -a: >> Linux server 2.6.27.7-smp #2 SMP Thu Nov 20 22:32:43 CST 2008 i686 >> Pentium III (Katmai) GenuineIntel GNU/Linux >> Slackware 12.2 is running on that kernel and my source for the server part is: > > Whatever is causing the leak isn't in the portion of the code which > you posted. > > Also: > >> struct sockaddr_un client_name; >> socklen_t client_name_len = 0; // it should be >= 0 otherwise accept returns EINVAL >> int client_socket_fd; >> client_socket_fd = accept(socket_fd, &client_name, &client_name_len); > > If you want accept to initialise client_name, you should initialise > client_name_len to the size of the buffer, i.e.: > > client_name_len = sizeof client_name; > > -- > Glynn Clements <glynn@xxxxxxxxxxxxxxxxxx> > -- > 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 > -- 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
