visus
/
toolchain-gcc-arm-embedded
İzle 1
Yıldızla 0
Çatalla 0
Kod Sorunlar 0 Değişiklik İstekleri 0 Sürümler 0 Wiki Aktivite
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
2 İşlemeler
1 Dal
Ağaç: 898a39b5ab
Dallar Biçim İmleri
${ item.name }
Branş ${ searchTerm } oluştur
'898a39b5ab'den
${ noResults }
toolchain-gcc-arm-embedded/share/doc/gcc-arm-none-eabi/html/gdb/Inline-Functions.html

134 satır
6.4KB
Ham Bahset Geçmiş 

  1. <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">

  2. <html>

  3. <!-- Copyright (C) 1988-2020 Free Software Foundation, Inc.

  4. 

  5. Permission is granted to copy, distribute and/or modify this document

  6. under the terms of the GNU Free Documentation License, Version 1.3 or

  7. any later version published by the Free Software Foundation; with the

  8. Invariant Sections being "Free Software" and "Free Software Needs

  9. Free Documentation", with the Front-Cover Texts being "A GNU Manual,"

  10. and with the Back-Cover Texts as in (a) below.

  11. 

  12. (a) The FSF's Back-Cover Text is: "You are free to copy and modify

  13. this GNU Manual.  Buying copies from GNU Press supports the FSF in

  14. developing GNU and promoting software freedom." -->

  15. <!-- Created by GNU Texinfo 6.5, http://www.gnu.org/software/texinfo/ -->

  16. <head>

  17. <meta http-equiv="Content-Type" content="text/html; charset=utf-8">

  18. <title>Inline Functions (Debugging with GDB)</title>

  19. 

  20. <meta name="description" content="Inline Functions (Debugging with GDB)">

  21. <meta name="keywords" content="Inline Functions (Debugging with GDB)">

  22. <meta name="resource-type" content="document">

  23. <meta name="distribution" content="global">

  24. <meta name="Generator" content="makeinfo">

  25. <link href="index.html#Top" rel="start" title="Top">

  26. <link href="Concept-Index.html#Concept-Index" rel="index" title="Concept Index">

  27. <link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">

  28. <link href="Optimized-Code.html#Optimized-Code" rel="up" title="Optimized Code">

  29. <link href="Tail-Call-Frames.html#Tail-Call-Frames" rel="next" title="Tail Call Frames">

  30. <link href="Optimized-Code.html#Optimized-Code" rel="prev" title="Optimized Code">

  31. <style type="text/css">

  32. <!--

  33. a.summary-letter {text-decoration: none}

  34. blockquote.indentedblock {margin-right: 0em}

  35. blockquote.smallindentedblock {margin-right: 0em; font-size: smaller}

  36. blockquote.smallquotation {font-size: smaller}

  37. div.display {margin-left: 3.2em}

  38. div.example {margin-left: 3.2em}

  39. div.lisp {margin-left: 3.2em}

  40. div.smalldisplay {margin-left: 3.2em}

  41. div.smallexample {margin-left: 3.2em}

  42. div.smalllisp {margin-left: 3.2em}

  43. kbd {font-style: oblique}

  44. pre.display {font-family: inherit}

  45. pre.format {font-family: inherit}

  46. pre.menu-comment {font-family: serif}

  47. pre.menu-preformatted {font-family: serif}

  48. pre.smalldisplay {font-family: inherit; font-size: smaller}

  49. pre.smallexample {font-size: smaller}

  50. pre.smallformat {font-family: inherit; font-size: smaller}

  51. pre.smalllisp {font-size: smaller}

  52. span.nolinebreak {white-space: nowrap}

  53. span.roman {font-family: initial; font-weight: normal}

  54. span.sansserif {font-family: sans-serif; font-weight: normal}

  55. ul.no-bullet {list-style: none}

  56. -->

  57. </style>

  58. 

  59. 

  60. </head>

  61. 

  62. <body lang="en">

  63. <a name="Inline-Functions"></a>

  64. <div class="header">

  65. <p>

  66. Next: <a href="Tail-Call-Frames.html#Tail-Call-Frames" accesskey="n" rel="next">Tail Call Frames</a>, Up: <a href="Optimized-Code.html#Optimized-Code" accesskey="u" rel="up">Optimized Code</a> &nbsp; [<a href="index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="Concept-Index.html#Concept-Index" title="Index" rel="index">Index</a>]</p>

  67. </div>

  68. <hr>

  69. <a name="Inline-Functions-1"></a>

  70. <h3 class="section">11.1 Inline Functions</h3>

  71. <a name="index-inline-functions_002c-debugging"></a>

  72. 

  73. <p><em>Inlining</em> is an optimization that inserts a copy of the function

  74. body directly at each call site, instead of jumping to a shared

  75. routine.  <small>GDB</small> displays inlined functions just like

  76. non-inlined functions.  They appear in backtraces.  You can view their

  77. arguments and local variables, step into them with <code>step</code>, skip

  78. them with <code>next</code>, and escape from them with <code>finish</code>.

  79. You can check whether a function was inlined by using the

  80. <code>info frame</code> command.

  81. </p>

  82. <p>For <small>GDB</small> to support inlined functions, the compiler must

  83. record information about inlining in the debug information &mdash;

  84. <small>GCC</small> using the <small>DWARF 2</small> format does this, and several

  85. other compilers do also.  <small>GDB</small> only supports inlined functions

  86. when using <small>DWARF 2</small>.  Versions of <small>GCC</small> before 4.1

  87. do not emit two required attributes (&lsquo;<samp>DW_AT_call_file</samp>&rsquo; and

  88. &lsquo;<samp>DW_AT_call_line</samp>&rsquo;); <small>GDB</small> does not display inlined

  89. function calls with earlier versions of <small>GCC</small>.  It instead

  90. displays the arguments and local variables of inlined functions as

  91. local variables in the caller.

  92. </p>

  93. <p>The body of an inlined function is directly included at its call site;

  94. unlike a non-inlined function, there are no instructions devoted to

  95. the call.  <small>GDB</small> still pretends that the call site and the

  96. start of the inlined function are different instructions.  Stepping to

  97. the call site shows the call site, and then stepping again shows

  98. the first line of the inlined function, even though no additional

  99. instructions are executed.

  100. </p>

  101. <p>This makes source-level debugging much clearer; you can see both the

  102. context of the call and then the effect of the call.  Only stepping by

  103. a single instruction using <code>stepi</code> or <code>nexti</code> does not do

  104. this; single instruction steps always show the inlined body.

  105. </p>

  106. <p>There are some ways that <small>GDB</small> does not pretend that inlined

  107. function calls are the same as normal calls:

  108. </p>

  109. <ul>

  110. <li> Setting breakpoints at the call site of an inlined function may not

  111. work, because the call site does not contain any code.  <small>GDB</small>

  112. may incorrectly move the breakpoint to the next line of the enclosing

  113. function, after the call.  This limitation will be removed in a future

  114. version of <small>GDB</small>; until then, set a breakpoint on an earlier line

  115. or inside the inlined function instead.

  116. 

  117. </li><li> <small>GDB</small> cannot locate the return value of inlined calls after

  118. using the <code>finish</code> command.  This is a limitation of compiler-generated

  119. debugging information; after <code>finish</code>, you can step to the next line

  120. and print a variable where your program stored the return value.

  121. 

  122. </li></ul>

  123. 

  124. <hr>

  125. <div class="header">

  126. <p>

  127. Next: <a href="Tail-Call-Frames.html#Tail-Call-Frames" accesskey="n" rel="next">Tail Call Frames</a>, Up: <a href="Optimized-Code.html#Optimized-Code" accesskey="u" rel="up">Optimized Code</a> &nbsp; [<a href="index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="Concept-Index.html#Concept-Index" title="Index" rel="index">Index</a>]</p>

  128. </div>

  129. 

  130. 

  131. 

  132. </body>

  133. </html>