From: Jean-Philippe Andriot <andriot@6WIND.com>
To: Mehmet Tek <mtek@ade.com>
Cc: linux-c-programming@vger.kernel.org
Subject: Re: Thread causing memory leaks...
Date: Mon, 22 Aug 2005 10:36:52 +0200 [thread overview]
Message-ID: <43098EA4.8050508@6WIND.com> (raw)
In-Reply-To: <200508191714586.SM02404@037f27dd816a40c>
Hi
You should use "pthread_exit" instead of "return NULL"
JP
Mehmet Tek wrote:
>Hi all,
>
>After debugging for a number of hours, I found out that the very basics of my
>thread usage is causing memory leaks. (I checked it with mtrace and valgrind,
>they both say that there is memory leak.)
>
>I have a very simple program below that leaks memory. Can anyone tell me if I
>am doing sth wrong, or is it actually some bug in the native thread
>implementation?
>
>Any feedback would be appreciated...
>
>Thanks,
>Mehmet
>
>PS: I am using Linux 2.4.21 (SuSE 9.0) with gcc 3.3.1 on a AMD64 machine.
>
>===========================================================================
>
>#include <iostream>
>#include <pthread.h>
>#include <mcheck.h>
>
>using namespace std;
>
>void *thFunction(void *arg) {
>
> cout << " Thread started" << endl;
>
> cout << " Thread ending" << endl;
>
> return NULL;
>
>}
>
>int main() {
>
> pthread_t th;
>
> // mtrace();
>
> cout << " Spawning the thread" << endl;
>
> pthread_create(&th, NULL, thFunction, NULL);
>
> pthread_join(th, NULL);
>
> // muntrace();
>
> return 0;
>}
>
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
>
>
>
next parent reply other threads:[~2005-08-22 8:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200508191714586.SM02404@037f27dd816a40c>
2005-08-22 8:36 ` Jean-Philippe Andriot [this message]
2005-08-19 13:37 Thread causing memory leaks Mehmet Tek
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=43098EA4.8050508@6WIND.com \
--to=andriot@6wind.com \
--cc=linux-c-programming@vger.kernel.org \
--cc=mtek@ade.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.