• <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++ Programmer's Cookbook

            {C++ 基礎} {C++ 高級} {C#界面,C++核心算法} {設計模式} {C#基礎}

            調試breakpoint高級

            breakpoint的右鍵菜單:
            o_tiaoshi2.jpg

            Tracepoints

            When you have a "mystery" bug to solve, tracepoints are a vital part of your debugging arsenal. Single stepping and looking through code can be S-L-O-O-O-O-W and if you don't even know what you're looking for, it can consume hours and hours of effort. Tracepoints really speed things up. They're like breakpoints that don't break. In a way, they go back to the old "printf debugging" -- but you don't need to make code changes and recompile to change them.

            To set a tracepoint, first set a breakpoint, then right-click on the red dot that appears in the margin and choose When Hit:

            In the dialog that appears, click the Print A Message box and edit the starter message you are given. You can include any expression in braces and it will be evaluated when control reaches the tracepoint:

            Leave the Continue Execution box checked so that you don't break. Tracepoints are identified by red diamonds instead of red dots:

            The output from the tracepoints appears in the output window of your debug session:

            You can set up something suspicious, let it run, then pore through the tracepoint output and see what you learn. It's a huge timesaver when you're tackling a "we don't even know where to start" bug. Plus, if the issue is related to threading or async issues in any way (and you know me, I keep preaching we will all be facing async issues eventually) then you don't have to worry that pausing execution suppresses the collisions. I recently helped a client solve a big hairy this-stuff-fails-for-our-biggest-customer-only bug using tracepoints... and a few other tricks I will cover in upcoming posts.

            Conditional breakpoints

            Conditional breakpoints were another really important tool in solving a recent "only happens at the big installations" bug in a big and complicated C++ application. We wanted to debug the code with as few rebuilds as possible and we really didn't know how parts of it worked at all. Tracepoints helped us to figure out a lot of it in a short time. We didn't have a decent repro case though, so here's what we did:

            • created a script to add an audit table and some triggers that write to it
            • created a script to remove those triggers and the table
            • created a batch file to run a server in verbose mode, and redirect the output to a text file (remembering DOS commands sure can be helpful...   myapp.exe -verbose >logfile.txt was the magic phrase.)
            • wrote some instructions for the support guy to grab a backup of the database, run the first script, run the batch file, let it run all night, then in the morning grab another backup of the database, run the second script, and stop the batch file.

            Now we ran some queries on the morning version of the database to confirm that at least one X was missing a Y that should have been calculated overnight. We even had the Xid. Thanks to the tracepoint work of the previous day we knew where to be suspicious. A little digging in the trigger output told us whether the problem was "didn't get added" or "got added, but then got deleted". The last step was conditional breakpoints. These let us say "only stop here when you're processing the X with this Xid."

            This really saves time when you just need to drill into what's happening in the case that is going wrong. You get to it by right clicking the red dot or diamond and choosing Condition.


            One more breakpoint tip - hit count

            Conditional breakpoints are cool when you know the value of one variable that is associated with trouble: this only blows up when Xid is 1234. They can also be used to reduce the boredom of single stepping. Say you've got some loop that goes around a few hundred times building up some string or array or something. You don't want to keep going round and round and round... it would be nice to jump ahead to halfway through, for example, and see how things are looking. Now if this is a for loop with a handy named variable, say

             

            for (int i = 0; i<1000; i++)

             

            Then you can use a conditional breakpoint and say "stop when i is 200". Or you could be clever and stop when i % 200 is 0 -- so that's every 200 times. But what if there's no i? What if you're going through a file or a recordset/dataset/resultset and you're going until the end? You don't want to add some fake variable that gets incremented each time through the loop, just so you can set a breakpoint that breaks on certain values of that variable. Instead you want to use the hit count property of the breakpoint. Just right click the red dot and choose Hit Count. There you can set the breakpoint to break whenever it's hit, just the 10th time it's hit, every tenth time (10, 20, 30 etc) or every time after the 10th time Or, of course, whatever number you want instead of 10:

            Don't debug the slow way when there are tools to make you so much faster!

            Filter   下次再介紹:

            o_tiaoshi.jpg


            注意:c#的也可以用的啊....



            來自:http://www.gregcons.com/KateBlog/CategoryView.aspx?category=C%2B%2B

            posted on 2006-08-16 14:47 夢在天涯 閱讀(3040) 評論(0)  編輯 收藏 引用 所屬分類: CPlusPlusC#/.NETVS2005/2008

            公告

            EMail:itech001#126.com

            導航

            統計

            • 隨筆 - 461
            • 文章 - 4
            • 評論 - 746
            • 引用 - 0

            常用鏈接

            隨筆分類

            隨筆檔案

            收藏夾

            Blogs

            c#(csharp)

            C++(cpp)

            Enlish

            Forums(bbs)

            My self

            Often go

            Useful Webs

            Xml/Uml/html

            搜索

            •  

            積分與排名

            • 積分 - 1808098
            • 排名 - 5

            最新評論

            閱讀排行榜

            久久亚洲春色中文字幕久久久| 久久精品国产精品亚洲精品| 精品99久久aaa一级毛片| 久久精品国产只有精品66| 久久综合成人网| 97久久超碰国产精品旧版| 精品久久久久久国产三级| 伊人久久大香线蕉av一区| 97久久香蕉国产线看观看| 亚洲七七久久精品中文国产| 久久天天躁狠狠躁夜夜网站 | 国产婷婷成人久久Av免费高清| 久久精品国产91久久麻豆自制 | 亚洲精品美女久久久久99小说| 性高湖久久久久久久久| 国产真实乱对白精彩久久| 麻豆AV一区二区三区久久| 久久久久无码专区亚洲av| 久久精品国产免费| 欧美噜噜久久久XXX| 蜜桃麻豆WWW久久囤产精品| 久久久WWW成人免费毛片| 99国产欧美久久久精品蜜芽 | 五月丁香综合激情六月久久| 欧美激情精品久久久久久| 97久久精品人人澡人人爽| 国产精品99久久免费观看| 久久天天躁狠狠躁夜夜网站| 久久久久久综合网天天| 伊人久久国产免费观看视频 | 久久久91人妻无码精品蜜桃HD| 久久久久四虎国产精品| 国产精品一久久香蕉产线看| 久久久久久毛片免费播放| 久久丫精品国产亚洲av| 久久久久久久久久久久中文字幕| 精品综合久久久久久97| 伊人久久大香线焦AV综合影院 | 精品久久久久久久无码 | 色综合久久中文综合网| 九九99精品久久久久久|