This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[mi, doc] mention escape sequences


It does not seem that MI spec ever mentions escape sequence support
(where it's supported) or lack of such support. This patch tries to
fix that. 

Note that parse_escape function supports more than C language escape
sequences, it seems, but given that the function has no comments on
those sequences, and given that manual does not say anything about
that either, I don't feel like reverse-engineering the code to
document the exact rules. "As in C" as sufficient, I think, for MI
manual.

OK?

- Volodya
Index: gdb/doc/gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.504
diff -u -p -r1.504 gdb.texinfo
--- gdb/doc/gdb.texinfo	10 Jun 2008 10:23:53 -0000	1.504
+++ gdb/doc/gdb.texinfo	11 Jun 2008 14:04:34 -0000
@@ -18018,6 +18018,10 @@ list.  Each option is identified by a le
 followed by an optional argument parameter.  Options occur first in the
 parameter list and can be delimited from normal parameters using
 @samp{--} (this is useful when some parameters begin with a dash).
+
+@item
+Within @var{c-string}, all escape sequences allowed by the C language
+are recognized.  Escape sequences are not allowed in @var{non-blank-sequence}.
 @end itemize
 
 Pragmatics:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]