GDB function call tracing












1














Is there a way to attach a print statement to the call of a function? I would like to debug a x64 program with nested loops and logic and it would be faster to see the sequence of function calls by printing them as they occur, rather than setting breakpoints.



Can this be done with a post hook in gdb or a different technique?










share|improve this question



























    1














    Is there a way to attach a print statement to the call of a function? I would like to debug a x64 program with nested loops and logic and it would be faster to see the sequence of function calls by printing them as they occur, rather than setting breakpoints.



    Can this be done with a post hook in gdb or a different technique?










    share|improve this question

























      1












      1








      1







      Is there a way to attach a print statement to the call of a function? I would like to debug a x64 program with nested loops and logic and it would be faster to see the sequence of function calls by printing them as they occur, rather than setting breakpoints.



      Can this be done with a post hook in gdb or a different technique?










      share|improve this question













      Is there a way to attach a print statement to the call of a function? I would like to debug a x64 program with nested loops and logic and it would be faster to see the sequence of function calls by printing them as they occur, rather than setting breakpoints.



      Can this be done with a post hook in gdb or a different technique?







      gdb






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 23 '18 at 11:13









      jarryd

      14.3k47162273




      14.3k47162273
























          1 Answer
          1






          active

          oldest

          votes


















          1















          Is there a way to attach a print statement to the call of a function?




          Yes: attach a breakpoint to every function you want to trace, and attach commands to each of these breakpoints:



          (gdb) break foo
          (gdb) commands $bpnum
          continue
          end


          Now every time foo is called, GDB will print the usual "Breakpoint N ..." message, and then continue.



          Obviously you could print additional info (argument values, call stack, thread-id, etc.).



          You will probably want to set height 0 to disable pagination. You will also probably want to log this to a file (see set logging file, set logging on, etc.)






          share|improve this answer





















          • ah, nice. Thanks a lot.
            – jarryd
            Nov 24 '18 at 14:08











          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53445637%2fgdb-function-call-tracing%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          1















          Is there a way to attach a print statement to the call of a function?




          Yes: attach a breakpoint to every function you want to trace, and attach commands to each of these breakpoints:



          (gdb) break foo
          (gdb) commands $bpnum
          continue
          end


          Now every time foo is called, GDB will print the usual "Breakpoint N ..." message, and then continue.



          Obviously you could print additional info (argument values, call stack, thread-id, etc.).



          You will probably want to set height 0 to disable pagination. You will also probably want to log this to a file (see set logging file, set logging on, etc.)






          share|improve this answer





















          • ah, nice. Thanks a lot.
            – jarryd
            Nov 24 '18 at 14:08
















          1















          Is there a way to attach a print statement to the call of a function?




          Yes: attach a breakpoint to every function you want to trace, and attach commands to each of these breakpoints:



          (gdb) break foo
          (gdb) commands $bpnum
          continue
          end


          Now every time foo is called, GDB will print the usual "Breakpoint N ..." message, and then continue.



          Obviously you could print additional info (argument values, call stack, thread-id, etc.).



          You will probably want to set height 0 to disable pagination. You will also probably want to log this to a file (see set logging file, set logging on, etc.)






          share|improve this answer





















          • ah, nice. Thanks a lot.
            – jarryd
            Nov 24 '18 at 14:08














          1












          1








          1







          Is there a way to attach a print statement to the call of a function?




          Yes: attach a breakpoint to every function you want to trace, and attach commands to each of these breakpoints:



          (gdb) break foo
          (gdb) commands $bpnum
          continue
          end


          Now every time foo is called, GDB will print the usual "Breakpoint N ..." message, and then continue.



          Obviously you could print additional info (argument values, call stack, thread-id, etc.).



          You will probably want to set height 0 to disable pagination. You will also probably want to log this to a file (see set logging file, set logging on, etc.)






          share|improve this answer













          Is there a way to attach a print statement to the call of a function?




          Yes: attach a breakpoint to every function you want to trace, and attach commands to each of these breakpoints:



          (gdb) break foo
          (gdb) commands $bpnum
          continue
          end


          Now every time foo is called, GDB will print the usual "Breakpoint N ..." message, and then continue.



          Obviously you could print additional info (argument values, call stack, thread-id, etc.).



          You will probably want to set height 0 to disable pagination. You will also probably want to log this to a file (see set logging file, set logging on, etc.)







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Nov 23 '18 at 17:36









          Employed Russian

          123k19165233




          123k19165233












          • ah, nice. Thanks a lot.
            – jarryd
            Nov 24 '18 at 14:08


















          • ah, nice. Thanks a lot.
            – jarryd
            Nov 24 '18 at 14:08
















          ah, nice. Thanks a lot.
          – jarryd
          Nov 24 '18 at 14:08




          ah, nice. Thanks a lot.
          – jarryd
          Nov 24 '18 at 14:08


















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.





          Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


          Please pay close attention to the following guidance:


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53445637%2fgdb-function-call-tracing%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          A CLEAN and SIMPLE way to add appendices to Table of Contents and bookmarks

          Calculate evaluation metrics using cross_val_predict sklearn

          Insert data from modal to MySQL (multiple modal on website)