visus
/
toolchain-gcc-arm-embedded
Sledovat 1
Oblíbit 0
Rozštěpit 0
Zdrojový kód Úkoly 0 Požadavky na natažení 0 Vydání 0 Wiki Aktivita
Nelze vybrat více než 25 témat Téma musí začínat písmenem nebo číslem, může obsahovat pomlčky („-“) a může být dlouhé až 35 znaků.
2 Revize
1 Větev
Strom: 898a39b5ab
Větve Značky
${ item.name }
Vytvořit větev ${ searchTerm }
z „898a39b5ab“
${ noResults }
toolchain-gcc-arm-embedded/share/doc/gcc-arm-none-eabi/html/gdb/Thread-groups.html

120 lines
6.3KB
Surový Blame Historie 

  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>Thread groups (Debugging with GDB)</title>

  19. 

  20. <meta name="description" content="Thread groups (Debugging with GDB)">

  21. <meta name="keywords" content="Thread groups (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="GDB_002fMI-General-Design.html#GDB_002fMI-General-Design" rel="up" title="GDB/MI General Design">

  29. <link href="GDB_002fMI-Command-Syntax.html#GDB_002fMI-Command-Syntax" rel="next" title="GDB/MI Command Syntax">

  30. <link href="Asynchronous-and-non_002dstop-modes.html#Asynchronous-and-non_002dstop-modes" rel="prev" title="Asynchronous and non-stop modes">

  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="Thread-groups"></a>

  64. <div class="header">

  65. <p>

  66. Previous: <a href="Asynchronous-and-non_002dstop-modes.html#Asynchronous-and-non_002dstop-modes" accesskey="p" rel="prev">Asynchronous and non-stop modes</a>, Up: <a href="GDB_002fMI-General-Design.html#GDB_002fMI-General-Design" accesskey="u" rel="up">GDB/MI General Design</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="Thread-groups-1"></a>

  70. <h4 class="subsection">27.1.3 Thread groups</h4>

  71. <p><small>GDB</small> may be used to debug several processes at the same time.

  72. On some platforms, <small>GDB</small> may support debugging of several

  73. hardware systems, each one having several cores with several different

  74. processes running on each core.  This section describes the MI

  75. mechanism to support such debugging scenarios.

  76. </p>

  77. <p>The key observation is that regardless of the structure of the 

  78. target, MI can have a global list of threads, because most commands that 

  79. accept the &lsquo;<samp>--thread</samp>&rsquo; option do not need to know what process that

  80. thread belongs to.  Therefore, it is not necessary to introduce

  81. neither additional &lsquo;<samp>--process</samp>&rsquo; option, nor an notion of the

  82. current process in the MI interface.  The only strictly new feature

  83. that is required is the ability to find how the threads are grouped

  84. into processes.

  85. </p>

  86. <p>To allow the user to discover such grouping, and to support arbitrary

  87. hierarchy of machines/cores/processes, MI introduces the concept of a

  88. <em>thread group</em>.  Thread group is a collection of threads and other

  89. thread groups.  A thread group always has a string identifier, a type,

  90. and may have additional attributes specific to the type.  A new

  91. command, <code>-list-thread-groups</code>, returns the list of top-level

  92. thread groups, which correspond to processes that <small>GDB</small> is

  93. debugging at the moment.  By passing an identifier of a thread group

  94. to the <code>-list-thread-groups</code> command, it is possible to obtain

  95. the members of specific thread group.

  96. </p>

  97. <p>To allow the user to easily discover processes, and other objects, he

  98. wishes to debug, a concept of <em>available thread group</em> is

  99. introduced.  Available thread group is an thread group that

  100. <small>GDB</small> is not debugging, but that can be attached to, using the

  101. <code>-target-attach</code> command.  The list of available top-level thread

  102. groups can be obtained using &lsquo;<samp>-list-thread-groups --available</samp>&rsquo;.

  103. In general, the content of a thread group may be only retrieved only

  104. after attaching to that thread group.

  105. </p>

  106. <p>Thread groups are related to inferiors (see <a href="Inferiors-Connections-and-Programs.html#Inferiors-Connections-and-Programs">Inferiors Connections and Programs</a>).  Each inferior corresponds to a thread group of a special

  107. type &lsquo;<samp>process</samp>&rsquo;, and some additional operations are permitted on

  108. such thread groups.

  109. </p>

  110. <hr>

  111. <div class="header">

  112. <p>

  113. Previous: <a href="Asynchronous-and-non_002dstop-modes.html#Asynchronous-and-non_002dstop-modes" accesskey="p" rel="prev">Asynchronous and non-stop modes</a>, Up: <a href="GDB_002fMI-General-Design.html#GDB_002fMI-General-Design" accesskey="u" rel="up">GDB/MI General Design</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>

  114. </div>

  115. 

  116. 

  117. 

  118. </body>

  119. </html>