[18/26] gdbsupport: fix a typo in a comment in common-regcache.h

Message ID beb2b9a17a03a2e6d203b686ea64464e365b5c0a.1677582745.git.tankut.baris.aktemur@intel.com
State New
Headers
Series gdbserver: refactor regcache and allow gradually populating |

Commit Message

Aktemur, Tankut Baris Feb. 28, 2023, 11:28 a.m. UTC
  Fix a typo.
---
 gdbsupport/common-regcache.h | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)
  

Comments

Simon Marchi Dec. 22, 2023, 3:24 a.m. UTC | #1
On 2023-02-28 06:28, Tankut Baris Aktemur via Gdb-patches wrote:
> Fix a typo.
> ---
>  gdbsupport/common-regcache.h | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/gdbsupport/common-regcache.h b/gdbsupport/common-regcache.h
> index e462f532407..bf14610f98f 100644
> --- a/gdbsupport/common-regcache.h
> +++ b/gdbsupport/common-regcache.h
> @@ -33,10 +33,10 @@ enum register_status : signed char
>  
>      /* The register value is unavailable.  E.g., we're inspecting a
>         traceframe, and this register wasn't collected.  Note that this
> -       is different a different "unavailable" from saying the register
> -       does not exist in the target's architecture --- in that case,
> -       the target should have given us a target description that does
> -       not include the register in the first place.  */
> +       "unavailable" is different from saying the register does not
> +       exist in the target's architecture --- in that case, the target
> +       should have given us a target description that does not include
> +       the register in the first place.  */
>      REG_UNAVAILABLE = -1
>    };
>  

LGTM, I think that can be pushed right away.

Approved-By: Simon Marchi <simon.marchi@efficios.com>

Simon
  

Patch

diff --git a/gdbsupport/common-regcache.h b/gdbsupport/common-regcache.h
index e462f532407..bf14610f98f 100644
--- a/gdbsupport/common-regcache.h
+++ b/gdbsupport/common-regcache.h
@@ -33,10 +33,10 @@  enum register_status : signed char
 
     /* The register value is unavailable.  E.g., we're inspecting a
        traceframe, and this register wasn't collected.  Note that this
-       is different a different "unavailable" from saying the register
-       does not exist in the target's architecture --- in that case,
-       the target should have given us a target description that does
-       not include the register in the first place.  */
+       "unavailable" is different from saying the register does not
+       exist in the target's architecture --- in that case, the target
+       should have given us a target description that does not include
+       the register in the first place.  */
     REG_UNAVAILABLE = -1
   };