gdb_server: refuse gdb connection if target is not examined
authorAntonio Borneo <borneo.antonio@gmail.com>
Tue, 4 Jun 2019 10:06:44 +0000 (12:06 +0200)
committerAntonio Borneo <borneo.antonio@gmail.com>
Sat, 8 Aug 2020 21:17:31 +0000 (22:17 +0100)
commit2f92598f0d6d8304a9c15f7050c9e888279cd2fa
tree3c3a772192aa10ce874317a7606439398f12a085
parent6d45e485f98bb1712c0ec2f48c879ceaf6fd06ac
gdb_server: refuse gdb connection if target is not examined

If the target is not examined, many internal data required for the
gdb connections are not ready nor allocated. This causes OpenOCD
to hit a segmentation fault.

After the execution of the gdb-attach event handler, check if
target has been examined and eventually return error to refuse the
gdb connection.

Plus, since OpenOCD does not implements non-stop mode yet, gdb
expects the target to be halted by the inferior when the
connection is established.
Print a warning to inform the user in case the target is not
halted, but still accept the gdb connection to permit the
non-intrusive memory inspection with gdb, as explained in
http://openocd.org/doc/html/GDB-and-OpenOCD.html#gdbmeminspect

Change-Id: If727d68f683c3a94e4826e8c62977de41274ceff
Signed-off-by: Antonio Borneo <borneo.antonio@gmail.com>
Reviewed-on: http://openocd.zylin.com/5201
Tested-by: jenkins
src/server/gdb_server.c