From 6f700d2b1c57d40c6ce4e9972427334f89bbc96c Mon Sep 17 00:00:00 2001 From: Tomas Vanek Date: Tue, 13 Mar 2018 10:30:59 +0100 Subject: [PATCH] doc: make gdb-attach description understandable Change-Id: I31babf4e3bbe7c94f26818d938699562a4a26d48 Signed-off-by: Tomas Vanek Reviewed-on: http://openocd.zylin.com/4465 Tested-by: jenkins Reviewed-by: Paul Fertser --- doc/openocd.texi | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/doc/openocd.texi b/doc/openocd.texi index ce9cd3b96..4cc051ee4 100644 --- a/doc/openocd.texi +++ b/doc/openocd.texi @@ -4488,9 +4488,10 @@ The following target events are defined: @item @b{examine-end} @* After target examine is called with no errors. @item @b{gdb-attach} -@* When GDB connects. This is before any communication with the target and GDB -expects the target is halted during attachment. -@xref{gdbmeminspect,,GDB as a non-intrusive memory inspector} for exclusion. +@* When GDB connects. Issued before any GDB communication with the target +starts. GDB expects the target is halted during attachment. +@xref{gdbmeminspect,,GDB as a non-intrusive memory inspector}, how to +connect GDB to running target. The event can be also used to set up the target so it is possible to probe flash. Probing flash is necessary during GDB connect if you want to use @pxref{programmingusinggdb,,programming using GDB}.