public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
* [binutils-gdb] Remove call to registers_changed from windows-nat.c
@ 2022-12-01 18:42 Tom Tromey
0 siblings, 0 replies; only message in thread
From: Tom Tromey @ 2022-12-01 18:42 UTC (permalink / raw)
To: gdb-cvs
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=4cb80f0e5bddc29cf50b08f0a4d2cca8ea330a23
commit 4cb80f0e5bddc29cf50b08f0a4d2cca8ea330a23
Author: Tom Tromey <tromey@adacore.com>
Date: Wed Nov 30 13:50:27 2022 -0700
Remove call to registers_changed from windows-nat.c
I noticed that windows_nat_target::interrupt calls registers_changed.
However, I don't think there's any reason to do this, because this
will happen automatically when the inferior stop is processed.
Approved-By: Simon Marchi <simon.marchi@efficios.com>
Diff:
---
gdb/windows-nat.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/gdb/windows-nat.c b/gdb/windows-nat.c
index 900d8c3d3c4..b3329cd1a0d 100644
--- a/gdb/windows-nat.c
+++ b/gdb/windows-nat.c
@@ -2877,7 +2877,6 @@ windows_nat_target::interrupt ()
DEBUG_EVENTS ("GenerateConsoleCtrlEvent (CTRLC_EVENT, 0)");
CHECK (GenerateConsoleCtrlEvent (CTRL_C_EVENT,
windows_process.current_event.dwProcessId));
- registers_changed (); /* refresh register state */
}
/* Helper for windows_xfer_partial that handles memory transfers.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2022-12-01 18:42 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-12-01 18:42 [binutils-gdb] Remove call to registers_changed from windows-nat.c Tom Tromey
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).