diff options
| author | Pedro Alves <palves@redhat.com> | 2015-11-30 16:05:25 +0000 |
|---|---|---|
| committer | Pedro Alves <palves@redhat.com> | 2015-11-30 18:43:24 +0000 |
| commit | f2faf941ae49653ff6e1485adfee299313d47c91 (patch) | |
| tree | 6d494270ef0baff9c2490cb8b1643ab4139d14b7 /gdb/NEWS | |
| parent | f4836ba964a96364f39c7eab8b8b2f8656d14d05 (diff) | |
| download | gdb-f2faf941ae49653ff6e1485adfee299313d47c91.zip gdb-f2faf941ae49653ff6e1485adfee299313d47c91.tar.gz gdb-f2faf941ae49653ff6e1485adfee299313d47c91.tar.bz2 | |
Implement TARGET_WAITKIND_NO_RESUMED in the remote protocol
Testing with "maint set target-non-stop on" causes regressions in
tests that rely on TARGET_WAITKIND_NO_RESUMED, which isn't modelled on
the RSP. In real all-stop, gdbserver detects the situation and
reporst error to GDB, and so the tests (e.g.,
gdb.threads/no-unwaited-for-left.exp) at fail quickly. But with
"maint set target-non-stop on", GDB instead hangs forever waiting for
a stop reply that never comes, and so the tests take longer to time
out.
This adds a new "N" stop reply packet that maps 1-1 to
TARGET_WAITKIND_NO_RESUMED.
gdb/ChangeLog:
2015-11-30 Pedro Alves <palves@redhat.com>
PR 14618
* NEWS (New remote packets): Mention the N stop reply.
* remote.c (remote_protocol_features): Add "no-resumed" entry.
(remote_query_supported): Report no-resumed+ support.
(remote_parse_stop_reply): Handle 'N'.
(process_stop_reply): Handle TARGET_WAITKIND_NO_RESUMED.
(remote_wait_as): Handle 'N' / TARGET_WAITKIND_NO_RESUMED.
(_initialize_remote): Register "set/show remote
no-resumed-stop-reply" commands.
gdb/doc/ChangeLog:
2015-11-30 Pedro Alves <palves@redhat.com>
PR 14618
* gdb.texinfo (Stop Reply Packets): Document the N stop reply.
(Remote Configuration): Add the "set/show remote
no-resumed-stop-reply" to the available settings table.
(General Query Packets): Document the "no-resumed" qSupported
feature.
gdb/gdbserver/ChangeLog:
2015-11-30 Pedro Alves <palves@redhat.com>
PR 14618
* linux-low.c (linux_wait_1): If the last resumed thread is gone,
report TARGET_WAITKIND_NO_RESUMED.
* remote-utils.c (prepare_resume_reply): Handle
TARGET_WAITKIND_NO_RESUMED.
* server.c (report_no_resumed): New global.
(handle_query) <qSupported>: Handle "no-resumed+". Report
"no-resumed+" support.
(resume): When the target reports TARGET_WAITKIND_NO_RESUMED, only
return error if the client doesn't support no-resumed events.
(push_stop_notification): New function.
(handle_target_event): Use it. Report TARGET_WAITKIND_NO_RESUMED
events if the client supports them.
gdb/testsuite/ChangeLog:
2015-11-30 Pedro Alves <palves@redhat.com>
* gdb.threads/no-unwaited-for-left.exp: Remove setup_kfail calls.
Diffstat (limited to 'gdb/NEWS')
| -rw-r--r-- | gdb/NEWS | 6 |
1 files changed, 6 insertions, 0 deletions
@@ -106,6 +106,12 @@ QThreadEvents would hang forever not knowing that it should no longer expect a stop for that same thread. +N stop reply + + Indicates that there are no resumed threads left in the target (all + threads are stopped). The remote stub reports support for this stop + reply to GDB's qSupported query. + * Extended-remote exec events ** GDB now has support for exec events on extended-remote Linux targets. |