[v2,02/22] Update two cleanup comments
Commit Message
This updates another couple of comments to remove a mentions of
cleanups.
gdb/ChangeLog
2019-02-27 Tom Tromey <tom@tromey.com>
* inferior.h (class inferior): Update comment.
* gdbthread.h (class thread_info): Update comment.
---
gdb/ChangeLog | 5 +++++
gdb/gdbthread.h | 2 +-
gdb/inferior.h | 2 +-
3 files changed, 7 insertions(+), 2 deletions(-)
Comments
On 02/27/2019 08:18 PM, Tom Tromey wrote:
> This updates another couple of comments to remove a mentions of
> cleanups.
s/a mention/mensions/ ?
>
> gdb/ChangeLog
> 2019-02-27 Tom Tromey <tom@tromey.com>
>
> * inferior.h (class inferior): Update comment.
> * gdbthread.h (class thread_info): Update comment.
OK.
Thanks,
Pedro Alves
@@ -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
@@ -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. */