• <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 閱讀(2025) 評(píng)論(0)  編輯 收藏 引用

            只有注冊(cè)用戶登錄后才能發(fā)表評(píng)論。
            網(wǎng)站導(dǎo)航: 博客園   IT新聞   BlogJava   博問   Chat2DB   管理


            <2025年6月>
            25262728293031
            1234567
            891011121314
            15161718192021
            22232425262728
            293012345

            常用鏈接

            留言簿(1)

            隨筆檔案

            Friend

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

            搜索

            •  

            最新評(píng)論

            閱讀排行榜

            評(píng)論排行榜

            久久午夜电影网| 久久国产精品无码一区二区三区| 久久国产精品无码一区二区三区| 无码人妻久久一区二区三区免费丨| 午夜人妻久久久久久久久| 91精品国产高清91久久久久久| 日本精品久久久久中文字幕8| 久久精品国产精品亚洲| 久久这里的只有是精品23| 中文字幕人妻色偷偷久久| 99久久精品国产高清一区二区| 亚洲国产成人久久综合一| 久久久久久国产a免费观看黄色大片| 国产精品久久久久免费a∨| 久久99国产精一区二区三区| 日日狠狠久久偷偷色综合96蜜桃| 亚洲国产精品无码久久久秋霞2| 国内精品久久久久久久影视麻豆| 久久久久国产精品人妻| 国产亚洲美女精品久久久| 亚洲中文字幕无码久久2020| 精品久久久久久无码中文字幕| 久久香综合精品久久伊人| 亚洲人AV永久一区二区三区久久| 久久狠狠色狠狠色综合| 久久久久99精品成人片直播| 久久人妻AV中文字幕| 久久精品国产欧美日韩| 亚洲国产精品久久久久婷婷老年 | 久久久久久毛片免费看| 国产精品久久久久久久久免费| 国产精品亚洲综合久久 | 亚洲国产精品一区二区久久hs| 成人午夜精品久久久久久久小说| 狼狼综合久久久久综合网| 一本久久综合亚洲鲁鲁五月天| 精品久久人人妻人人做精品| 久久97精品久久久久久久不卡| 97r久久精品国产99国产精| 久久精品无码一区二区无码| 欧美牲交A欧牲交aⅴ久久|