[PATCH 07/10] [gdb/guile] Fix doc string for value-optimized-out?
Tom de Vries
tdevries@suse.de
Fri Jun 2 15:56:36 GMT 2023
In gdb/guile/scm-value.c, I noticed in the value_functions array initializer:
...
{ "value-optimized-out?", 1, 0, 0,
as_a_scm_t_subr (gdbscm_value_optimized_out_p),
"\
Return #t if the value has been optimizd out." },
...
There's a typo in the doc string.
Fix this by using "optimized".
---
gdb/guile/scm-value.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gdb/guile/scm-value.c b/gdb/guile/scm-value.c
index 32a9539b3e2..6f325db97ca 100644
--- a/gdb/guile/scm-value.c
+++ b/gdb/guile/scm-value.c
@@ -1358,7 +1358,7 @@ Typically this is used to convert numbers and strings to\n\
{ "value-optimized-out?", 1, 0, 0,
as_a_scm_t_subr (gdbscm_value_optimized_out_p),
"\
-Return #t if the value has been optimizd out." },
+Return #t if the value has been optimized out." },
{ "value-address", 1, 0, 0, as_a_scm_t_subr (gdbscm_value_address),
"\
--
2.35.3
More information about the Gdb-patches
mailing list