mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Re: cluts daily reports 8/12 - continuing pthread_eintr, still stuck with alloc
Date: Sat, 13 Aug 2011 14:43:08 -0400	[thread overview]
Message-ID: <20110813184308.GK132@brightrain.aerifal.cx> (raw)
In-Reply-To: <4E46C747.1080006@gmail.com>

On Sat, Aug 13, 2011 at 08:49:43PM +0200, Luka Marčetić wrote:
> pthread_exit is allegedly called upon main thread function return,
> and it is specified to pop and execute pushed functions. I expected

pthread_exit is called implicitly upon the return from the start
function of any thread *except* the main thread. pthread_exit does pop
and execute cleanup handlers when it's called, but if it's called
implcitly due to return from the start function, there cannot be any
cleanup handlers left because execution has already left the scope of
any cleanup handler that may have been installed.

> this to happen. I was blaming the spec for not being more specific,
> and saying that pthread_exit should be explicitly called. But in
> reality, perhaps even an implicit call should work, in which case
> the spec isn't to blame, but both implementations instead?

Could you please explain what effect you're trying to achieve? Cleanup
handlers are rather useless unless you're using pthread_cancel.

Rich


  reply	other threads:[~2011-08-13 18:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-12  2:45 Luka Marčetić
2011-08-12  2:41 ` Rich Felker
2011-08-12 15:40   ` Luka Marčetić
2011-08-12 15:39     ` Rich Felker
2011-08-13 18:49       ` Luka Marčetić
2011-08-13 18:43         ` Rich Felker [this message]
2011-08-13 19:03           ` Luka Marčetić
2011-08-12  2:47 ` Rich Felker
2011-08-12  3:13   ` Solar Designer
2011-08-12 15:48     ` Luka Marčetić
2011-08-12  3:12 ` Rich Felker

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=20110813184308.GK132@brightrain.aerifal.cx \
    --to=dalias@aerifal.cx \
    --cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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).