diff options
| author | Roland Schwarz <roland.schwarz@blackspace.at> | 2006-12-14 18:55:51 +0000 |
|---|---|---|
| committer | Roland Schwarz <roland.schwarz@blackspace.at> | 2006-12-14 18:55:51 +0000 |
| commit | c15911fe286ac9ef0c7167ce6f058257cc17f2f6 (patch) | |
| tree | 3ef7015efab10a13fe189f72af1f7cc2bc18a4c2 /status | |
| parent | 1909e576b260dc8d743e8175b3415c35e1233b98 (diff) | |
| download | boost-c15911fe286ac9ef0c7167ce6f058257cc17f2f6.tar.gz | |
Explained expected test_tss_lib failures.
[SVN r36388]
Diffstat (limited to 'status')
| -rw-r--r-- | status/explicit-failures-markup.xml | 17 |
1 files changed, 17 insertions, 0 deletions
diff --git a/status/explicit-failures-markup.xml b/status/explicit-failures-markup.xml index 8354650044..67c2efe324 100644 --- a/status/explicit-failures-markup.xml +++ b/status/explicit-failures-markup.xml @@ -3710,6 +3710,23 @@ for more information. <toolset name="qcc-3.3*"/> <note author="Jim Douglas" date="13 Feb 06" refid="16"/> </mark-expected-failures> + <mark-expected-failures> + <test name="test_tss_lib"/> + <toolset name="*"/> + <note author="Roland Schwarz" date="2006-12-14"> + When a thread ends, tss data needs to be cleaned up. This process + is mostly automatic. When threads are launched by the Boost.Thread API + cleanup is handled by the library implementation. For threads, launched + by the native operating system API it is not possible to get this cleanup + on every compiler/platform. A warning (error) will be present in this case, + which cleary states this fact. It is recommended to start threads only + by means of the Boost.Thread API if you need to avoid the leaks that appear + on the end of the thread. If this is not possible the cleanup can be invoked + from user code before the process actually ends. For library implementors + this means to call these functions during library initialization and + finalization. + </note> + </mark-expected-failures> </library> <!-- tuple --> |