• <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>
            posts - 9,  comments - 9,  trackbacks - 0

            Normally, the break instruction exception can be triggered in following conditions:

            1.       Hardcode interrupt request, like: __asm int 3 (ASM), System.Diagnostics.Debugger.Break (C#), DebugBreak() (WinAPI).

            2.       OS enable memory runtime check, like Application Verifier can trigger after heap corruption, memory overrun.

            3.       Compiler can have some configuration to decide what should be filled to the uninitialized memory block and end of function(blank area, after retun..).  For example, Microsoft VC complier can fill 0xCC if enable /GZ.  0xCC is actually a opcode of __asm int 3.  So if some error cause the application run into such block, will trigger a break point.

            A quick summary of what Microsoft's compilers use for various bits of unowned/uninitialized memory when compiled for debug mode (support may vary by compiler version):

            Value     Name           Description 

            ------   --------        -------------------------

            0xCD     Clean Memory    Allocated memory via malloc or new but never 

                                     written by the application. 


            0xDD     Dead Memory     Memory that has been released with delete or free. 

                                     Used to detect writing through dangling pointers. 


            0xFD     Fence Memory    Also known as "no mans land." This is used to wrap 

                                     the allocated memory (surrounding it with a fence) 

                                     and is used to detect indexing arrays out of 

                                     bounds or other accesses (especially writes) past

                                     the end (or start) of an allocated block.


            0xCC                     When the code is compiled with the /GZ option,

                                     uninitialized variables are automatically assigned 

                                     to this value (at byte level). 



            // the following magic values are done by the OS, not the C runtime:


            0xAB  (Allocated Block?) Memory allocated by LocalAlloc(). 


            0xBAADF00D Bad Food      Memory allocated by LocalAlloc() with LMEM_FIXED,but 

                                     not yet written to. 


            0xFEEEFEEE               OS fill heap memory, which was marked for usage, 

                                     but wasn't allocated by HeapAlloc() or LocalAlloc(). 

                                     Or that memory just has been freed by HeapFree().

            Disclaimer: the table is from some notes I have lying around - they may not be 100% correct (or coherent).


            As others have noted, one of the key properties of these values is that is a pointer variable with one of these values is dereferenced, it will result in an access violation, since on a standard 32-bit Windows configuration, user mode addresses will not go higher than 0x7fffffff.


            For the related issue, we can use Application Verifier to enable heap page, which can break after memory overrun, heap corruption.


             

             

            posted on 2010-07-23 16:22 MicroYang 閱讀(2028) 評論(0)  編輯 收藏 引用
            <2025年7月>
            293012345
            6789101112
            13141516171819
            20212223242526
            272829303112
            3456789

            常用鏈接

            留言簿(1)

            隨筆檔案

            Friend

            • Catherine
            • 深海羚羊
            • 似雨打芭蕉,似風吹梧桐葉,帶著一絲冰冷,也帶著一絲清新------冰柔語絲

            搜索

            •  

            最新評論

            閱讀排行榜

            評論排行榜

            99久久人妻无码精品系列| 性欧美大战久久久久久久久| 久久久精品午夜免费不卡| 国内精品久久久久伊人av| 国产精品伦理久久久久久| 欧美久久亚洲精品| 久久综合精品国产二区无码| 2020最新久久久视精品爱 | 久久人人妻人人爽人人爽| 久久久久国产精品| 久久天天躁狠狠躁夜夜avapp| 久久久久亚洲精品天堂| 四虎亚洲国产成人久久精品| 99久久这里只有精品| 国产精品乱码久久久久久软件| 国产精品久久久久久一区二区三区 | 国产精品免费久久| 日韩久久久久久中文人妻| 日本久久中文字幕| 97精品国产97久久久久久免费| 精品久久久无码人妻中文字幕 | 久久人人爽人人爽人人片AV不| 久久久免费观成人影院| 久久综合久久自在自线精品自| 久久91精品国产91| 色婷婷噜噜久久国产精品12p| 伊人久久免费视频| 91精品日韩人妻无码久久不卡| 久久亚洲精品中文字幕| 欧美牲交A欧牲交aⅴ久久| 狠狠色丁香婷婷久久综合| 日批日出水久久亚洲精品tv| 日本精品久久久久久久久免费| 99久久精品国产一区二区三区| 亚洲欧美精品伊人久久| 99久久精品免费观看国产| 国产精品久久久久久久久久免费| 精品久久久久中文字| 久久性精品| 精品久久久久久国产| 久久久国产精品亚洲一区|