Thread-groups.html 6.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120
  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. Permission is granted to copy, distribute and/or modify this document
  5. under the terms of the GNU Free Documentation License, Version 1.3 or
  6. any later version published by the Free Software Foundation; with the
  7. Invariant Sections being "Free Software" and "Free Software Needs
  8. Free Documentation", with the Front-Cover Texts being "A GNU Manual,"
  9. and with the Back-Cover Texts as in (a) below.
  10. (a) The FSF's Back-Cover Text is: "You are free to copy and modify
  11. this GNU Manual. Buying copies from GNU Press supports the FSF in
  12. developing GNU and promoting software freedom." -->
  13. <!-- Created by GNU Texinfo 5.1, http://www.gnu.org/software/texinfo/ -->
  14. <head>
  15. <title>Debugging with GDB: Thread groups</title>
  16. <meta name="description" content="Debugging with GDB: Thread groups">
  17. <meta name="keywords" content="Debugging with GDB: Thread groups">
  18. <meta name="resource-type" content="document">
  19. <meta name="distribution" content="global">
  20. <meta name="Generator" content="makeinfo">
  21. <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  22. <link href="index.html#Top" rel="start" title="Top">
  23. <link href="Concept-Index.html#Concept-Index" rel="index" title="Concept Index">
  24. <link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
  25. <link href="GDB_002fMI-General-Design.html#GDB_002fMI-General-Design" rel="up" title="GDB/MI General Design">
  26. <link href="GDB_002fMI-Command-Syntax.html#GDB_002fMI-Command-Syntax" rel="next" title="GDB/MI Command Syntax">
  27. <link href="Asynchronous-and-non_002dstop-modes.html#Asynchronous-and-non_002dstop-modes" rel="previous" title="Asynchronous and non-stop modes">
  28. <style type="text/css">
  29. <!--
  30. a.summary-letter {text-decoration: none}
  31. blockquote.smallquotation {font-size: smaller}
  32. div.display {margin-left: 3.2em}
  33. div.example {margin-left: 3.2em}
  34. div.indentedblock {margin-left: 3.2em}
  35. div.lisp {margin-left: 3.2em}
  36. div.smalldisplay {margin-left: 3.2em}
  37. div.smallexample {margin-left: 3.2em}
  38. div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
  39. div.smalllisp {margin-left: 3.2em}
  40. kbd {font-style:oblique}
  41. pre.display {font-family: inherit}
  42. pre.format {font-family: inherit}
  43. pre.menu-comment {font-family: serif}
  44. pre.menu-preformatted {font-family: serif}
  45. pre.smalldisplay {font-family: inherit; font-size: smaller}
  46. pre.smallexample {font-size: smaller}
  47. pre.smallformat {font-family: inherit; font-size: smaller}
  48. pre.smalllisp {font-size: smaller}
  49. span.nocodebreak {white-space:nowrap}
  50. span.nolinebreak {white-space:nowrap}
  51. span.roman {font-family:serif; font-weight:normal}
  52. span.sansserif {font-family:sans-serif; font-weight:normal}
  53. ul.no-bullet {list-style: none}
  54. -->
  55. </style>
  56. </head>
  57. <body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#800080" alink="#FF0000">
  58. <a name="Thread-groups"></a>
  59. <div class="header">
  60. <p>
  61. Previous: <a href="Asynchronous-and-non_002dstop-modes.html#Asynchronous-and-non_002dstop-modes" accesskey="p" rel="previous">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>
  62. </div>
  63. <hr>
  64. <a name="Thread-groups-1"></a>
  65. <h4 class="subsection">27.1.3 Thread groups</h4>
  66. <p><small>GDB</small> may be used to debug several processes at the same time.
  67. On some platforms, <small>GDB</small> may support debugging of several
  68. hardware systems, each one having several cores with several different
  69. processes running on each core. This section describes the MI
  70. mechanism to support such debugging scenarios.
  71. </p>
  72. <p>The key observation is that regardless of the structure of the
  73. target, MI can have a global list of threads, because most commands that
  74. accept the &lsquo;<samp>--thread</samp>&rsquo; option do not need to know what process that
  75. thread belongs to. Therefore, it is not necessary to introduce
  76. neither additional &lsquo;<samp>--process</samp>&rsquo; option, nor an notion of the
  77. current process in the MI interface. The only strictly new feature
  78. that is required is the ability to find how the threads are grouped
  79. into processes.
  80. </p>
  81. <p>To allow the user to discover such grouping, and to support arbitrary
  82. hierarchy of machines/cores/processes, MI introduces the concept of a
  83. <em>thread group</em>. Thread group is a collection of threads and other
  84. thread groups. A thread group always has a string identifier, a type,
  85. and may have additional attributes specific to the type. A new
  86. command, <code>-list-thread-groups</code>, returns the list of top-level
  87. thread groups, which correspond to processes that <small>GDB</small> is
  88. debugging at the moment. By passing an identifier of a thread group
  89. to the <code>-list-thread-groups</code> command, it is possible to obtain
  90. the members of specific thread group.
  91. </p>
  92. <p>To allow the user to easily discover processes, and other objects, he
  93. wishes to debug, a concept of <em>available thread group</em> is
  94. introduced. Available thread group is an thread group that
  95. <small>GDB</small> is not debugging, but that can be attached to, using the
  96. <code>-target-attach</code> command. The list of available top-level thread
  97. groups can be obtained using &lsquo;<samp>-list-thread-groups --available</samp>&rsquo;.
  98. In general, the content of a thread group may be only retrieved only
  99. after attaching to that thread group.
  100. </p>
  101. <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
  102. type &lsquo;<samp>process</samp>&rsquo;, and some additional operations are permitted on
  103. such thread groups.
  104. </p>
  105. <hr>
  106. <div class="header">
  107. <p>
  108. Previous: <a href="Asynchronous-and-non_002dstop-modes.html#Asynchronous-and-non_002dstop-modes" accesskey="p" rel="previous">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>
  109. </div>
  110. </body>
  111. </html>