• <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 閱讀(2107) 評論(0)  編輯 收藏 引用 所屬分類: C++并發和并行 concurrency & parallelism

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

            導航

            統計

            常用鏈接

            留言簿(1)

            隨筆分類

            隨筆檔案

            搜索

            最新評論

            閱讀排行榜

            評論排行榜

            亚洲精品tv久久久久| 欧美性大战久久久久久| 国产精品久久久久久福利69堂| 国产成人精品久久一区二区三区| 久久免费小视频| 午夜精品久久影院蜜桃| 精品永久久福利一区二区| 久久久青草青青国产亚洲免观| 久久精品视频91| 久久久一本精品99久久精品88| 国产精品青草久久久久婷婷| 久久久久久极精品久久久 | 99久久国产综合精品网成人影院 | 7777精品久久久大香线蕉| 亚洲女久久久噜噜噜熟女| 国产精品一区二区久久精品无码| 免费久久人人爽人人爽av| 久久婷婷国产麻豆91天堂| 精品一二三区久久aaa片| 久久国产精品波多野结衣AV| 久久精品午夜一区二区福利| 久久亚洲中文字幕精品一区| segui久久国产精品| 久久国产精品久久国产精品| 久久香综合精品久久伊人| 久久人人爽人人爽人人片AV高清| 一本一道久久a久久精品综合| 久久精品国产69国产精品亚洲| 伊人久久大香线蕉av一区| 久久精品无码av| 久久久久九国产精品| 久久涩综合| 久久亚洲精品成人无码网站| 亚洲伊人久久成综合人影院 | 国产精品9999久久久久| 国产成人精品综合久久久久| 精品无码久久久久国产动漫3d| 久久精品国产亚洲AV忘忧草18| 综合久久精品色| 老男人久久青草av高清| 综合久久国产九一剧情麻豆|