• <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
            久久国产精品-久久精品| 999久久久免费精品国产| 久久精品夜色噜噜亚洲A∨| 精品无码人妻久久久久久| 日韩十八禁一区二区久久| 国产精品久久久久免费a∨| 伊人久久精品无码av一区| 久久免费小视频| 久久午夜夜伦鲁鲁片免费无码影视 | 久久WWW免费人成一看片| 久久夜色精品国产噜噜麻豆| 国产精品久久99| 国产精品久久久久久久人人看| 久久久久久久久久久久中文字幕| 久久美女人爽女人爽| 思思久久99热只有频精品66| 曰曰摸天天摸人人看久久久| 97精品依人久久久大香线蕉97| 久久国产精品99久久久久久老狼| 久久久久亚洲AV无码观看| 青青草原综合久久| 久久精品人妻中文系列| 国产—久久香蕉国产线看观看| 一本色道久久99一综合| 最新久久免费视频| 久久e热在这里只有国产中文精品99 | 久久免费视频网站| 精品国产乱码久久久久久1区2区| 青春久久| 亚洲国产精品成人AV无码久久综合影院 | 久久久久久久精品妇女99| 久久亚洲国产成人影院网站| 精品乱码久久久久久夜夜嗨 | 伊人久久成人成综合网222| 久久99精品久久久久久齐齐| 国产精品成人99久久久久91gav| 香蕉久久夜色精品升级完成| av色综合久久天堂av色综合在| 亚洲AⅤ优女AV综合久久久| 久久精品成人一区二区三区| 久久久久女教师免费一区|