• <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>

            S.l.e!ep.¢%

            像打了激速一樣,以四倍的速度運轉,開心的工作
            簡單、開放、平等的公司文化;尊重個性、自由與個人價值;
            posts - 1098, comments - 335, trackbacks - 0, articles - 1
              C++博客 :: 首頁 :: 新隨筆 :: 聯系 :: 聚合  :: 管理

            內存崩潰的BUG (3)

            Posted on 2009-04-01 13:35 S.l.e!ep.¢% 閱讀(1717) 評論(3)  編輯 收藏 引用 所屬分類: WinDbg

            內存崩潰的BUG
            內存崩潰的BUG (2)

            在昨天的調試中,感謝JayZ
            -----------------------------------------------------------------------------------------------------
            地址段034bd000 - 00007000沒法訪問。

            看調用棧0012e50c 0042ffc3 00000400 034c0fec 00000001 ws2_32!WSASend+0x61

            WSASend的第二個參數為034c0fec很不幸的落在這個區間內。看WSASend的原型
            int WSASend(
            __in SOCKET s,
            __in LPWSABUF lpBuffers,
            __in DWORD dwBufferCount,
            __out LPDWORD lpNumberOfBytesSent,
            __in DWORD dwFlags,
            __in LPWSAOVERLAPPED lpOverlapped,
            __in LPWSAOVERLAPPED_COMPLETION_ROUTINE lpCompletionRoutine
            );
            顯然第二個參數lpBuffers的地址非法。

            call stack frame往上就是你的代碼了:
            0012f580 0040e577 0012f5bc 00000014 0012f58c xxx.exe+xxx-function

            你需要在這里確認一下為什么傳出的lpBuffers指向一個錯誤的地址
            -------------------------------------------------------------------------------------------------------

            傳入 WSASend 的第二個參數 lpBuffers 確實指向了一個錯誤的地址,
            用 knL + .frame + x
            查看了?? xxx.exe+xxx-function???? 的局部變量,發現

            -------------------------------------------------------------------------------------------------------
            PER_IO_CONTEXT* overlappedEx=new PER_IO_CONTEXT;????? 發現??overlappedEx ?這個指針已經指向的內存是不對的
            overlappedEx->IOOperation= WRITE;
            overlappedEx->wsabuf.buf= (char *)malloc( nLen );
            if( NULL == overlappedEx->wsabuf.buf )
            {
            delete overlappedEx;
            return -1;
            }

            if(WSASend(m_socket,&(overlappedEx->wsabuf), 0x01,
            &(overlappedEx->dwBytes), overlappedEx->dwFlags,
            &(overlappedEx->Overlapped), NULL ) == SOCKET_ERROR)
            {

            在IOCP通知后,會 delete overlappedEx
            -------------------------------------------------------------------------------------------------------

            懷疑是不是 overlappedEx 這個指針的值被其它地方修改了?
            于是在局數變量中定義了多一個變量,在 WSASend 調用前,加多這個語句,

            PER_IO_CONTEXT* p? = overlappedEx;

            等了幾個小時,再次重現問題,

            用 knL + .frame + x
            查看了?? xxx.exe+xxx-function???? 的局部變量,發現

            p 的值跟 overlappedEx 還是相等的, 但它們指向的內存卻是

            0366fe8c p = 0x03443fd8
            0:010> !address 0x03443fd8
            ??? 03442000 : 03442000 - 00007000
            ??????????????????? Type???? 00000000
            ??????????????????? Protect? 00000001 PAGE_NOACCESS
            ??????????????????? State??? 00010000 MEM_FREE????????????????
            ??????????????????? Usage??? RegionUsageFree
            0:010> dd 0x03443fd8
            03443fd8? ???????? ???????? ???????? ????????
            03443fe8? ???????? ???????? ???????? ????????
            03443ff8? ???????? ???????? ???????? ????????
            03444008? ???????? ???????? ???????? ????????
            03444018? ???????? ???????? ???????? ????????
            03444028? ???????? ???????? ???????? ????????
            03444038? ???????? ???????? ???????? ????????
            03444048? ???????? ???????? ???????? ????????

            0:010> KB
            ChildEBP RetAddr? Args to Child?????????????
            0366edac 71a26294 00000668 03443fec 00000001 mswsock!WSPSend+0x243
            0366ede8 00430027 00000668 03443fec 00000001 ws2_32!WSASend+0x77

            初步結論是: 在執行到? mswsock!WSPSend+0x243 ,在 WSASend 上一層 new 出來的? PER_IO_CONTEXT 已經被 delete 了

            Feedback

            # re: 內存崩潰的BUG (3)   回復  更多評論   

            2009-04-02 00:15 by JayZ
            看如下輸出:
            03442000 : 03442000 - 00007000
            Type 00000000
            Protect 00000001 PAGE_NOACCESS
            State 00010000 MEM_FREE
            Usage RegionUsageFree
            這個內存段甚至已經不屬于Heap了(RegionUsageFree)。

            建議放個條件斷點在VirtualFree里面,來看一下這個內存段什么時候被free掉的。從call stack上面應該很容易就能發現問題。

            # re: 內存崩潰的BUG (3)   回復  更多評論   

            2009-04-02 08:36 by guest
            下內存斷點來監視,看看到底是被誰給改了。

            # re: 內存崩潰的BUG (3)   回復  更多評論   

            2009-04-02 12:17 by S.l.e!ep.¢%
            -------------------------------------------------------------------------------------------------------
            PER_IO_CONTEXT* overlappedEx=new PER_IO_CONTEXT; 發現 overlappedEx 這個指針已經指向的內存是不對的
            overlappedEx->IOOperation= WRITE;
            overlappedEx->wsabuf.buf= (char *)malloc( nLen );
            if( NULL == overlappedEx->wsabuf.buf )
            {
            delete overlappedEx;
            return -1;
            }

            if(WSASend(m_socket,&(overlappedEx->wsabuf), 0x01,
            &dwBytes, 0,
            &(overlappedEx->Overlapped), NULL ) == SOCKET_ERROR)
            {

            在IOCP通知后,會 delete overlappedEx
            -------------------------------------------------------------------------------------------------------

            今天直接用 Windbg 啟動程序,在 在IOCP通知后,會 delete overlappedEx 用 OutPutDebugString 打日志,
            發現 在 delete overlappedEx 后,
            WSASend 還會訪問到 overlappedEx
            国产精品久久久久久久app| 久久水蜜桃亚洲av无码精品麻豆| 久久一日本道色综合久久| 色婷婷综合久久久久中文| 国产精品一久久香蕉国产线看| 青青草国产精品久久| 久久综合日本熟妇| 久久发布国产伦子伦精品 | 久久精品一区二区三区中文字幕| 久久青青草原精品国产软件 | 色综合久久久久综合99| 久久精品中文字幕一区| 四虎国产永久免费久久| 99久久无色码中文字幕人妻| 久久综合九色综合97_久久久| 久久久国产亚洲精品| 久久午夜电影网| 精品久久久久久国产潘金莲| 四虎影视久久久免费观看| 久久精品无码一区二区三区| 久久久久久久综合狠狠综合| yellow中文字幕久久网| 99精品久久精品一区二区| 久久精品国产AV一区二区三区 | 99久久99久久精品国产片果冻| 中文字幕久久精品| 欧美性大战久久久久久| 久久国产视屏| 久久久噜噜噜久久| 国产激情久久久久影院| 91精品国产色综久久| 一级做a爰片久久毛片16| 国产精品久久久久影院色| 久久精品中文闷骚内射| www久久久天天com| 国产精品久久久久aaaa| 精品免费tv久久久久久久| 99久久综合狠狠综合久久止| 国产亚洲综合久久系列| 久久精品免费观看| 久久国产热这里只有精品|