public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug nptl/14609] Stack clobbering in pthread cancellation cleanup handlers Date: Sun, 23 Sep 2012 19:25:00 -0000 [thread overview] Message-ID: <bug-14609-131-dtkhRXWQNR@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-14609-131@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=14609 --- Comment #1 from joseph at codesourcery dot com <joseph at codesourcery dot com> 2012-09-23 19:24:58 UTC --- To quote the Rationale for the 1996 edition of POSIX.1 (since various bits of POSIX rationale may well not have ended up integrated in the versions of POSIX based on the Single Unix Specification), "it is an explicit goal of this standard to be compatible with existing exception facilities and languages having exceptions" (B.18.1.3 Thread Cancellation Cleanup Handlers, page 579, lines 9213-9215). Then, B.18.2.3 Establishing Cancellation Handlers, page 582, lines 9312-9314, "A more ambitious implementation of these routines might do even better by allowing the compiler to note that the cancellation cleanup handler is a constant and can be expanded inline.". And B.18.3 Language-Independent Cancellation Functionality, page 585, lines 9455-9459: "It is intended that bindings be able to use language exception facilities as part of the implementation of thread cancellation. In particular, it would be desirable to have thread cancellation, cancellation scopes, and their associated cleanup code map into exception raise, exception scopes, and exception handlers in languages providing them.". I think that exceptions, associated unwinding and execution of cleanup handlers in the context where pthread_cleanup_push was called were pretty clearly intended to be allowed as an approach for implementing cancellation. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next prev parent reply other threads:[~2012-09-23 19:25 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-09-22 23:47 [Bug nptl/14609] New: " bugdal at aerifal dot cx 2012-09-23 19:25 ` joseph at codesourcery dot com [this message] 2014-06-25 6:47 ` [Bug nptl/14609] " fweimer at redhat dot com 2014-06-25 6:50 ` bugdal at aerifal dot cx
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=bug-14609-131-dtkhRXWQNR@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@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: linkBe 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).