diff options
| author | Simon Marchi <simon.marchi@ericsson.com> | 2017-01-12 11:15:01 -0500 |
|---|---|---|
| committer | Simon Marchi <simon.marchi@ericsson.com> | 2017-01-12 11:15:02 -0500 |
| commit | 3015c06465584a437261c65a397fbd8f1a71aae7 (patch) | |
| tree | 51039d7ed1c7ace87caa4177f39aa8721844a399 /gdb/remote.c | |
| parent | fde1b17d37fd5557a22948d500bb5f4b6ef5d089 (diff) | |
| download | gdb-3015c06465584a437261c65a397fbd8f1a71aae7.zip gdb-3015c06465584a437261c65a397fbd8f1a71aae7.tar.gz gdb-3015c06465584a437261c65a397fbd8f1a71aae7.tar.bz2 | |
Update comment in remote_can_async_p
I find this comment counter intuitive, and it probably predates the
always-target-async change. AFAIK, remote will always be async, unless
the user explicitly prevents it with "maint set target-async off".
gdb/ChangeLog:
* remote.c (remote_can_async_p): Update comment.
Diffstat (limited to 'gdb/remote.c')
| -rw-r--r-- | gdb/remote.c | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/gdb/remote.c b/gdb/remote.c index 837b9ee..c73c30a 100644 --- a/gdb/remote.c +++ b/gdb/remote.c @@ -13653,8 +13653,9 @@ remote_can_async_p (struct target_ops *ops) { struct remote_state *rs = get_remote_state (); + /* We don't go async if the user has explicitly prevented it with the + "maint set target-async" command. */ if (!target_async_permitted) - /* We only enable async when the user specifically asks for it. */ return 0; /* We're async whenever the serial device is. */ |