public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Pedro Alves <palves@sourceware.org>
To: gdb-cvs@sourceware.org
Subject: [binutils-gdb] Remove infrun_thread_thread_exit observer
Date: Mon, 27 Feb 2023 19:14:52 +0000 (GMT)	[thread overview]
Message-ID: <20230227191452.38EEC3858C50@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=9b955acd7f5029345e7bd8e31a4af0e6b356f0ae

commit 9b955acd7f5029345e7bd8e31a4af0e6b356f0ae
Author: Pedro Alves <pedro@palves.net>
Date:   Wed Nov 16 17:01:44 2022 +0000

    Remove infrun_thread_thread_exit observer
    
    After the previous patches, I believe this observer isn't necessary
    anymore for anything.  Remove it.
    
    Change-Id: Idb33fb6b6f55589c8c523a92169b3ca95a23d0b9

Diff:
---
 gdb/infrun.c | 9 ---------
 1 file changed, 9 deletions(-)

diff --git a/gdb/infrun.c b/gdb/infrun.c
index beb9ca79389..79e1a6abd2a 100644
--- a/gdb/infrun.c
+++ b/gdb/infrun.c
@@ -3606,14 +3606,6 @@ infrun_thread_stop_requested (ptid_t ptid)
     }
 }
 
-static void
-infrun_thread_thread_exit (struct thread_info *tp, int silent)
-{
-  if (target_last_proc_target == tp->inf->process_target ()
-      && target_last_wait_ptid == tp->ptid)
-    nullify_last_target_wait_ptid ();
-}
-
 /* Delete the step resume, single-step and longjmp/exception resume
    breakpoints of TP.  */
 
@@ -10023,7 +10015,6 @@ enabled by default on some platforms."),
 					      "infrun");
   gdb::observers::thread_stop_requested.attach (infrun_thread_stop_requested,
 						"infrun");
-  gdb::observers::thread_exit.attach (infrun_thread_thread_exit, "infrun");
   gdb::observers::inferior_exit.attach (infrun_inferior_exit, "infrun");
   gdb::observers::inferior_execd.attach (infrun_inferior_execd, "infrun");

                 reply	other threads:[~2023-02-27 19:14 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=20230227191452.38EEC3858C50@sourceware.org \
    --to=palves@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: link
Be 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).