OpenE2K
/
binutils-gdb
12
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

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.
This commit is contained in:
Simon Marchi 2017-01-12 11:15:01 -05:00
parent fde1b17d37
commit 3015c06465
2 changed files with 6 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
gdb/ChangeLog
View File

@ -1,3 +1,7 @@
2017-01-12 Simon Marchi <simon.marchi@ericsson.com>
* remote.c (remote_can_async_p): Update comment.
2017-01-12 Simon Marchi <simon.marchi@ericsson.com>
* linux-nat.c (linux_nat_can_async_p): Update comment.

3
gdb/remote.c
View File

@ -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. */