From: ern0 <ern0@linkbroker.hu>
To: linux-c-programming <linux-c-programming@vger.kernel.org>
Subject: Re: Help on a memory leak issue
Date: Mon, 11 Jan 2010 21:17:50 +0100 [thread overview]
Message-ID: <4B4B876E.8030902@linkbroker.hu> (raw)
In-Reply-To: <8eec89ee1001110705k3257bd80r2a719a67b0bda641@mail.gmail.com>
> 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?
next prev parent reply other threads:[~2010-01-11 20:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-11 15:05 Help on a memory leak issue Uğur ATA
2010-01-11 20:17 ` ern0 [this message]
2010-01-11 20:37 ` Glynn Clements
2010-01-12 8:02 ` Sam Liao
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B4B876E.8030902@linkbroker.hu \
--to=ern0@linkbroker.hu \
--cc=linux-c-programming@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).