diff options
author | Antonio Borneo <borneo.antonio@gmail.com> | 2020-10-15 14:45:27 +0200 |
---|---|---|
committer | Antonio Borneo <borneo.antonio@gmail.com> | 2020-11-04 17:37:59 +0000 |
commit | e2e8a5f467e8e35618ce4fbf16b8da4e682d8258 (patch) | |
tree | 5b200e7d3b599606143b36149f64182775759565 /src/target/dsp5680xx.h | |
parent | 360b2c27012f3f787382bee9ce0b4e4707b22dc3 (diff) | |
download | riscv-openocd-e2e8a5f467e8e35618ce4fbf16b8da4e682d8258.zip riscv-openocd-e2e8a5f467e8e35618ce4fbf16b8da4e682d8258.tar.gz riscv-openocd-e2e8a5f467e8e35618ce4fbf16b8da4e682d8258.tar.bz2 |
gdb_server: allow multiple GDB connections to selected targets
The default way of working is to have a single GDB attached to one
target, so OpenOCD accepts only one connection to the GDB port of
each targets and rejects any further connection.
There are some barely safe use cases in which it could get useful
having a second GDB connection to the same target.
One such use case is while using GDB as a 'non-intrusive memory
inspector', as explained in the OpenOCD documentation.
One GDB can be left running an infinite loop to dump some memory
area, or even analysing the content, while keeping a second GDB
ready for user interaction or spot memory check.
Add a target configure option to specify the maximum number of GDB
connections allowed for that target, keeping the default to 1.
Change-Id: I4985a602e61588df0b527d2f2aa5b955c93e125e
Signed-off-by: Antonio Borneo <borneo.antonio@gmail.com>
Reviewed-on: http://openocd.zylin.com/5865
Tested-by: jenkins
Reviewed-by: Tarek BOCHKATI <tarek.bouchkati@gmail.com>
Diffstat (limited to 'src/target/dsp5680xx.h')
0 files changed, 0 insertions, 0 deletions