• <ins id="pjuwb"></ins>
    <blockquote id="pjuwb"><pre id="pjuwb"></pre></blockquote>
    <noscript id="pjuwb"></noscript>
          <sup id="pjuwb"><pre id="pjuwb"></pre></sup>
            <dd id="pjuwb"></dd>
            <abbr id="pjuwb"></abbr>

            C++ library系列 -- static destructors in multiple threads

              In VC++ 8.0, while  code compiled with /clr or /clr:pure, static destructors sometimes would not being properly called before process exites in multiple threads.

              CRT incorrectly set a lock at _global_unlock which resulted in such issue.

              In CLR-mixed mode, during the inialization of static local object, CRT would call _atexit_m(_CPVFV func) in msilexit.cpp to register a special __clrcall callback function which would be called back to destroy such static object when the current AppDomain quited.

              In the multithread environment, _atexit_helper which was invoked by _atexit_m, could register such callbace function successfully because it had been guarded by __global_lock() and __global_unlock(). But in the same environment, the _atexit_m would fail to assign the correct value to __onexitbegin_m and __onexitend_m.

              __onexitbegin_m and __onexitend_m were shared by the different threads; It's the key point of such issue. For example, the following statements,

              __onexitbegin_m = (_CPVFV *)_encode_pointer(onexitbegin_m);
              __onexitend_m = (_CPVFV *)_encode_pointer(onexitend_m);

            should also guarded by __global_lock() and __global_unlock() or other syn primitives.


            __global_lock();
            __onexitbegin_m = (_CPVFV *)_encode_pointer(onexitbegin_m);
            __onexitend_m   = (_CPVFV *)_encode_pointer(onexitend_m);
            __global_unlock();


            extern "C" int __clrcall _atexit_m(_CPVFV func)
            {
             MANAGED_ASSERT(AppDomain::CurrentDomain->IsDefaultAppDomain(), "This fuction must be called in the default domain");

             __global_lock();
             _CPVFV* onexitbegin_m = (_CPVFV*)_decode_pointer(__onexitbegin_m);
             _CPVFV* onexitend_m = (_CPVFV*)_decode_pointer(__onexitend_m);
             __global_unlock();

             int retval = _atexit_helper((_CPVFV)_encode_pointer(func), &__exit_list_size, &onexitend_m, &onexitbegin_m);

             __global_lock();
             __onexitbegin_m = (_CPVFV*)_encode_pointer(onexitbegin_m);
             __onexitend_m  = (_CPVFV*)_encode_pointer(onexitend_m);
             __global_unlock();

             return retval;
            }

            posted on 2011-02-08 20:57 flagman 閱讀(2105) 評論(0)  編輯 收藏 引用 所屬分類: C++并發(fā)和并行 concurrency & parallelism

            <2025年7月>
            293012345
            6789101112
            13141516171819
            20212223242526
            272829303112
            3456789

            導(dǎo)航

            統(tǒng)計

            常用鏈接

            留言簿(1)

            隨筆分類

            隨筆檔案

            搜索

            最新評論

            閱讀排行榜

            評論排行榜

            无码任你躁久久久久久老妇| 欧美综合天天夜夜久久| 欧美亚洲国产精品久久高清| 亚洲人成网亚洲欧洲无码久久| 精品久久无码中文字幕| 久久久久国产精品嫩草影院| 久久99精品久久久大学生| 青青草国产精品久久久久| 波多野结衣久久一区二区| 久久亚洲精品中文字幕三区| 久久影院久久香蕉国产线看观看| 欧美熟妇另类久久久久久不卡| 国产L精品国产亚洲区久久| 精品久久久无码人妻中文字幕| 国产激情久久久久影院小草| 久久国产亚洲精品无码| 久久妇女高潮几次MBA| 久久一区二区免费播放| 99久久精品无码一区二区毛片 | 女同久久| 久久精品亚洲福利| 国产一区二区精品久久| 久久香综合精品久久伊人| 国产精品久久久久久五月尺| 久久人人爽人人爽AV片| 久久国产香蕉视频| 久久精品二区| 久久久久黑人强伦姧人妻| 久久国产热这里只有精品| 久久久久综合中文字幕 | 久久精品国内一区二区三区| 久久久久亚洲AV成人片 | 久久精品亚洲男人的天堂| 亚洲午夜久久影院| 四虎国产永久免费久久| 99热都是精品久久久久久| 国产精品伊人久久伊人电影 | 日批日出水久久亚洲精品tv| 久久影院久久香蕉国产线看观看| 色婷婷久久久SWAG精品| 久久久久久国产精品无码下载 |