Re: [PATCH] thread cancellation via C++ exception

--===============0516753655==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="tsOsTdHNUZQcU9Ye"
Content-Disposition: inline


--tsOsTdHNUZQcU9Ye
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Ulrich Drepper <[email protected]> writes:


> This is not only not going to be added to glibc,

No illusions about that.


> it's also not guaranteed to work (probably doesn't work today) and=20
> can break in interesting ways at any time.

Are you talking about my patch or about the idea of finalizing=20
the exception?


> Cancellation, as the word already suggests, is final.  There mustn't be
> any catch without rethrow.  The thread library does, and will probably
> even more so in future, alter the state of the library once a thread is
> canceled and this is not reversible.

Agree. My patch prevents exception finalization in about the same way as
the original nptl code does.


-boris

--tsOsTdHNUZQcU9Ye
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iQGVAwUBQKoq1siAKQuuCE8dAQKezAv+LEvSq7DTPyxpvGLe6T1RzYEuRJyGmEsC
PU9sfWnFzN4+5KQb04bM6B/MQthPcTPbLBaSEy0Rbp5NVOe7AOneUWUxSqexEJ+x
74aij0kUazl7CzZB6WosDVQwpsHqdyIujaSKLwm9jrlY56jTJkuoVI2dx8JhOgQt
or895zpXaNfnSycP2/LFN9hutnF0AGKYx7F56AChIpR5VK1CzmTx6jQ5xFzir++S
mgwD34YlEfGru4OO65b7KCtrs3aShr/Lzw+vi/kqVE93kIZSPRYn/mvXVZ8Z9XaQ
m4J2lxyBGsGhh2/Gw66bg9lzn0kGD5iYXZgXrdK696MLuNzMEhHemItkw4dJWqut
tTSTPcyD6k8xawHKZTgoxoM+4UigUKzQ1ssU6qw5u/6jDM4RrRKaDAmXYysMNAqX
8emjFuZ69z8oZTxmq42Hp0VmQ3IxSEikkpR0hR5w+KJDlyi84hxHoPTu2kODPcbV
HEJn4sl2+mdPfJSnBw4TOwkCDIcMy/GG
=/jw/
-----END PGP SIGNATURE-----

--tsOsTdHNUZQcU9Ye--



--===============0516753655==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline