Skip to main content
path: root/doc
diff options
authorJohn Cortell2010-04-22 19:03:58 -0400
committerJohn Cortell2010-04-22 19:03:58 -0400
commita2f1be9effcb9a0951e6a59b2d10feb0879d975d (patch)
tree12838860a09246cfc98af5f29c714ae095716b1a /doc
parente26d82f4d58dc18014867ff89254f057762a4a12 (diff)
[280631] Thread list in Debug view not updated with non-Linux target
Diffstat (limited to 'doc')
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/org.eclipse.cdt.doc.user/contexts_CDT_DEBUGGER_DSFGDB.xml b/doc/org.eclipse.cdt.doc.user/contexts_CDT_DEBUGGER_DSFGDB.xml
index dab118ca0d..fe21208971 100644
--- a/doc/org.eclipse.cdt.doc.user/contexts_CDT_DEBUGGER_DSFGDB.xml
+++ b/doc/org.eclipse.cdt.doc.user/contexts_CDT_DEBUGGER_DSFGDB.xml
@@ -15,6 +15,9 @@
<description>Control the behavior of the C/C++ debugger when debugging with GDB, specifically when using a GDB (DSF) launcher.</description>
<topic href="reference/cdt_u_dsfgdb.htm" label="GDB Preferences"/>
+<context id="update_threadlist_button_context" title="About this checkbox">
+ <description>This checkbox controls whether the CDT debugger will ask gdb for the target program&apos;s thread list on each suspend event (breakpoint-hit, step, etc). Normally, this isn&apos;t necessary, as GDB sends notifications in realtime when a thread is created or destroyed. However, some lightweight GDB remote stubs won&apos;t send these notifications. As such, the CDT debugger doesn&apos;t find out about new or destroyed threads unless it polls gdb. Turn on this option if you are debugging such a target (typically an embedded one).</description>

Back to the top