server: gdb: always print target information in multi-target setups
When multiple targets are declared, it's not always obvious which target the connection was made for, this can lead to very confusing errors. Reported by zjason on IRC. Change-Id: I52906320394e89cb6cfe82054a3f94b27c999689 Signed-off-by: Paul Fertser <fercerpav@gmail.com> Reviewed-on: http://openocd.zylin.com/4135 Tested-by: jenkinscompliance_dev
parent
b95e0c13aa
commit
12a838c6d4
|
@ -991,7 +991,9 @@ static int gdb_new_connection(struct connection *connection)
|
|||
}
|
||||
|
||||
gdb_actual_connections++;
|
||||
LOG_DEBUG("New GDB Connection: %d, Target %s, state: %s",
|
||||
log_printf_lf(all_targets->next != NULL ? LOG_LVL_INFO : LOG_LVL_DEBUG,
|
||||
__FILE__, __LINE__, __func__,
|
||||
"New GDB Connection: %d, Target %s, state: %s",
|
||||
gdb_actual_connections,
|
||||
target_name(target),
|
||||
target_state_name(target));
|
||||
|
|
Loading…
Reference in New Issue