[PATCH] gdb/record-full: fix stop status when inferior isn't resumed

[Guinevere Larsen <guinevere@redhat.com>]

The wait function for the record-full target has a check for whether
or not the inferior should be resumed. However, when we correctly
identified that it shouldn't be resumed, we incorrectly set the exit
status as "ignore", as though the inferior had resumed and had an
uninteresting stop.

This would cause a problem when - for example - GDB has to wait for
all threads to actually be stopped, because we do that by waiting all
threads have a wait status of "no_resumed", and the "ignore" status
would make us iterate over them and wait more.

This commit fixes that by setting the status correctly to not_resumed.
---
 gdb/record-full.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gdb/record-full.c b/gdb/record-full.c
index 26bd85d34f6..f56b3dfc7fd 100644
--- a/gdb/record-full.c
+++ b/gdb/record-full.c
@@ -1188,7 +1188,7 @@ record_full_wait_1 (struct target_ops *ops,
       gdb_assert ((options & TARGET_WNOHANG) != 0);
 
       /* No interesting event.  */
-      status->set_ignore ();
+      status->set_no_resumed ();
       return minus_one_ptid;
     }
 

base-commit: ca0665335ff67af94f9ded026d7ef2405a68c453
-- 
2.55.0