From 9a6cf3683df4f85f58ccea00864e36dc9ebef2ef Mon Sep 17 00:00:00 2001 From: Gary Benson Date: Mon, 22 Sep 2014 11:33:59 +0100 Subject: [PATCH] Update target_stop's documentation This commit updates target_stop's documentation to clarify that it is asynchronous. gdb/ChangeLog: * target.c (target_stop): Updated comment. --- gdb/ChangeLog | 4 ++++ gdb/target.h | 6 ++++-- 2 files changed, 8 insertions(+), 2 deletions(-) diff --git a/gdb/ChangeLog b/gdb/ChangeLog index 48e39df1a8..35ecebcafd 100644 --- a/gdb/ChangeLog +++ b/gdb/ChangeLog @@ -1,3 +1,7 @@ +2014-09-22 Gary Benson + + * target.c (target_stop): Updated comment. + 2014-09-22 Gary Benson * target/target.h (target_stop_ptid): Renamed as... diff --git a/gdb/target.h b/gdb/target.h index 2ea7a2d83f..a6792282ec 100644 --- a/gdb/target.h +++ b/gdb/target.h @@ -1573,8 +1573,10 @@ extern int target_thread_alive (ptid_t ptid); extern void target_find_new_threads (void); /* Make target stop in a continuable fashion. (For instance, under - Unix, this should act like SIGSTOP). This function is normally - used by GUIs to implement a stop button. */ + Unix, this should act like SIGSTOP). Note that this function is + asynchronous: it does not wait for the target to become stopped + before returning. If this is the behavior you want please use + target_stop_and_wait. */ extern void target_stop (ptid_t ptid); -- 2.34.1