diff options
| author | Antonio Borneo <borneo.antonio@gmail.com> | 2020-03-16 14:53:18 +0100 |
|---|---|---|
| committer | Antonio Borneo <borneo.antonio@gmail.com> | 2020-04-12 22:03:55 +0100 |
| commit | 16706256e43cfdf6eb6b66e98f12f7a77f142edb (patch) | |
| tree | 73234658f34d55902c3c8a4f4da6049efaacf263 /src/server | |
| parent | 17ac52360fc27eed9f58506a102a32b653d4d48c (diff) | |
| download | riscv-openocd-16706256e43cfdf6eb6b66e98f12f7a77f142edb.zip riscv-openocd-16706256e43cfdf6eb6b66e98f12f7a77f142edb.tar.gz riscv-openocd-16706256e43cfdf6eb6b66e98f12f7a77f142edb.tar.bz2 | |
gdb_server: print the target associated to the gdb port
While running OpenOCD on multi-target SoC, it's not immediate to
detect which target is associated to each GDB port. The log only
reports:
Info : Listening on port 3333 for gdb connections
and a verbose debug log is required to get such info.
Promote to LOG_INFO() the existing debug message that already
reports the association, obtaining for each port:
Info : starting gdb server for stm32mp15x.cpu0 on 3333
Info : Listening on port 3333 for gdb connections
Change-Id: I1bd75655a3449222c959e6e82f5e0f8f5acd908a
Signed-off-by: Antonio Borneo <borneo.antonio@gmail.com>
Reviewed-on: http://openocd.zylin.com/5525
Tested-by: jenkins
Reviewed-by: Jan Matyas <matyas@codasip.com>
Reviewed-by: Tarek BOCHKATI <tarek.bouchkati@gmail.com>
Diffstat (limited to 'src/server')
| -rw-r--r-- | src/server/gdb_server.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/server/gdb_server.c b/src/server/gdb_server.c index 0ca4fa4..3f2632b 100644 --- a/src/server/gdb_server.c +++ b/src/server/gdb_server.c @@ -3489,7 +3489,7 @@ static int gdb_target_start(struct target *target, const char *port) if (NULL == gdb_service) return -ENOMEM; - LOG_DEBUG("starting gdb server for %s on %s", target_name(target), port); + LOG_INFO("starting gdb server for %s on %s", target_name(target), port); gdb_service->target = target; gdb_service->core[0] = -1; |