From: "Stephen Croall" <scroall@tibco.com>
To: "Giuliano Catrambone" <giuliano.catrambone@catrasoftware.it>
Cc: <pthreads-win32@sources.redhat.com>
Subject: RE: Memory leak with detached threads
Date: Sun, 29 Oct 2006 19:02:00 -0000 [thread overview]
Message-ID: <5D819E730A717F47BC9B256CCE55297001C410D6@NA-PA-VBE02.na.tibco.com> (raw)
DOH!
Just realised that you are calling pthread_attr_setdetachstate(). You
could change to calling pthread_detach() to see if the memory leak still
happens. We use this call a lot in our code and have no problems with
leaks.
Steve.
next reply other threads:[~2006-10-29 19:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-29 19:02 Stephen Croall [this message]
2006-10-29 20:10 ` Giuliano Catrambone
-- strict thread matches above, loose matches on Subject: below --
2006-10-29 18:54 Stephen Croall
2006-10-29 18:42 Giuliano Catrambone
2006-10-29 20:20 ` Tim Theisen
2006-10-30 22:03 ` Giuliano Catrambone
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=5D819E730A717F47BC9B256CCE55297001C410D6@NA-PA-VBE02.na.tibco.com \
--to=scroall@tibco.com \
--cc=giuliano.catrambone@catrasoftware.it \
--cc=pthreads-win32@sources.redhat.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).