public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Tom Tromey <tromey@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] Remove call to registers_changed from windows-nat.c Date: Thu, 1 Dec 2022 18:42:03 +0000 (GMT) [thread overview] Message-ID: <20221201184203.F2B1C3858D3C@sourceware.org> (raw) 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.
reply other threads:[~2022-12-01 18:42 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20221201184203.F2B1C3858D3C@sourceware.org \ --to=tromey@sourceware.org \ --cc=gdb-cvs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).