aboutsummaryrefslogtreecommitdiff
path: root/src/server
diff options
context:
space:
mode:
authorAnton Kolesov <akolesov@synopsys.com>2013-08-27 13:38:50 +0400
committerSpencer Oliver <spen@spen-soft.co.uk>2013-09-13 19:35:09 +0000
commitb8a23f1c43fd87f36ce454fbc7a6ea2534dcf52d (patch)
tree4b3699fb3740f746dc5fd0a097c5cc2538b01852 /src/server
parent8b3f0f3f69a393151252d7f2211c9a15ae6cb456 (diff)
gdb_server: Do not set gdb_con->sync to true for new connections
In GDB connected to OpenOCD there is a command "monitor gdb_sync" which makes next stepi command to be ignored while GDB still will get an updated target state. This command sets gdb_connection->sync field to true to notify that stepi should be ignored. This field is set to true for all new connection and is set to false after first "continue" command. However if first resume command is stepi/nexti then it will be ignored and result will confuse GDB client, it will report that target received signal SIGINT. This patch sets this field to false for new connections, thus stepi/nexti will work properly when it is a first resume command. Change-Id: I7c9ebd69c3dc35f3e316041aa99f4e9d3425c0b6 Signed-off-by: Anton Kolesov <akolesov@synopsys.com> Reviewed-on: http://openocd.zylin.com/1587 Tested-by: jenkins Reviewed-by: Andreas Fritiofson <andreas.fritiofson@gmail.com>
Diffstat (limited to 'src/server')
-rw-r--r--src/server/gdb_server.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/server/gdb_server.c b/src/server/gdb_server.c
index ab7d40d7..b9c8e5e8 100644
--- a/src/server/gdb_server.c
+++ b/src/server/gdb_server.c
@@ -906,7 +906,7 @@ static int gdb_new_connection(struct connection *connection)
gdb_connection->closed = 0;
gdb_connection->busy = 0;
gdb_connection->noack_mode = 0;
- gdb_connection->sync = true;
+ gdb_connection->sync = false;
gdb_connection->mem_write_error = false;
gdb_connection->attached = true;