This is the mail archive of the
mailing list for the GDB project.
Re: GDB/MI escape characters
- From: Bob Rossi <bob at brasko dot net>
- To: gdb at sourceware dot org
- Date: Wed, 30 Jul 2014 06:45:56 -0400
- Subject: Re: GDB/MI escape characters
- Authentication-results: sourceware.org; auth=none
- References: <20140728010303 dot GA10702 at linux>
On Sun, Jul 27, 2014 at 09:03:03PM -0400, Bob Rossi wrote:
> Does anyone know what characters GDB escapes in the GDB/MI protocol
> above and beyond what would otherwise be escaped from the CLI?
> For instance if i print the variable p,
> char *p = "aaa\"aaa\naaa\raaa\\aaa";
> from the cli I get,
> (gdb) p p
> $1 = 0x400584 "aaa\"aaa\naaa\raaa\\aaa"
> from MI I get,
> p p
> ~"$2 = 0x400584 \"aaa\\\"aaa\\naaa\\raaa\\\\aaa\""
> From the output I can see that \ and " are escaped in MI output above
> and beyond what is escaped in the CLI. Are there other characters that
> would be?
> The function mi-out.c:mi_field_string might be a clue?
I've determined that the quoting explicitely happens for c-string's
rules in the grammar here,
I was debugging gdb and got to utils.c, this function,
the quoter parameter is ".
So I think I've determined that in general, gdb will escape \ to \\
and " to \" so the gdb/mi client has to undo that. Make sense?
I was pretty suprised to see in that example that the ESC character goes
to \e, but only in some situations.