[binutils-gdb] Update two cleanup comments

[Tom Tromey <tromey at sourceware dot org>]

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

commit 09e3c4ca13e39b797b91b07280ac025327a8a526
Author: Tom Tromey <tom@tromey.com>
Date:   Wed Jan 23 15:11:42 2019 -0700

    Update two cleanup comments
    
    This updates another couple of comments to remove mentions of
    cleanups.
    
    gdb/ChangeLog
    2019-03-06  Tom Tromey  <tom@tromey.com>
    
    	* inferior.h (class inferior): Update comment.
    	* gdbthread.h (class thread_info): Update comment.

Diff:
---
 gdb/ChangeLog   | 5 +++++
 gdb/gdbthread.h | 2 +-
 gdb/inferior.h  | 2 +-
 3 files changed, 7 insertions(+), 2 deletions(-)

diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index b17b6a9..11878bd 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,8 @@
+2019-03-06  Tom Tromey  <tom@tromey.com>
+
+	* inferior.h (class inferior): Update comment.
+	* gdbthread.h (class thread_info): Update comment.
+
 2019-03-06  Joel Brobecker  <brobecker@adacore.com>
 	    Tom Tromey  <tom@tromey.com>
 
diff --git a/gdb/gdbthread.h b/gdb/gdbthread.h
index 3b9d569..2d497d5 100644
--- a/gdb/gdbthread.h
+++ b/gdb/gdbthread.h
@@ -235,7 +235,7 @@ struct private_thread_info
    reverting back (e.g., due to a "kill" command).  If the thread
    meanwhile exits before being re-selected, then the thread object is
    left listed in the thread list, but marked with state
-   THREAD_EXITED.  (See make_cleanup_restore_current_thread and
+   THREAD_EXITED.  (See scoped_restore_current_thread and
    delete_thread).  All other thread references are considered weak
    references.  Placing a thread in the thread list is an implicit
    strong reference, and is thus not accounted for in the thread's
diff --git a/gdb/inferior.h b/gdb/inferior.h
index 2d1bb97..f98e67d 100644
--- a/gdb/inferior.h
+++ b/gdb/inferior.h
@@ -335,7 +335,7 @@ extern void set_current_inferior (inferior *);
    the inferior object's refcount, to prevent something deleting the
    inferior object before reverting back (e.g., due to a
    "remove-inferiors" command (see
-   make_cleanup_restore_current_thread).  All other inferior
+   scoped_restore_current_inferior).  All other inferior
    references are considered weak references.  Inferiors are always
    listed exactly once in the inferior list, so placing an inferior in
    the inferior list is an implicit, not counted strong reference.  */