* =tsv-created MI event outputs extra "\n" on MI channel
@ 2018-10-10 9:39 Jan Vrany
0 siblings, 0 replies; only message in thread
From: Jan Vrany @ 2018-10-10 9:39 UTC (permalink / raw)
To: gdb
Hi,
I just discovered that =tsv-created event contains an extra \n at the end
(i mean, backslash + n):
gdbserver localhost:1234 ./factorial1
then
gdb -i mi2 -ex "target extended-remote localhost:1234"
produces:
<a lot of stuff, cut for brevity>
~"Remote debugging using localhost:1234\n"
=tsv-created,name="trace_timestamp",initial="0"\n
(gdb)
Note the literal \n at the end of =tsv-created. This is IMO not
a valid MI record, according to documentation.
Looking at the code, this has been introduced in commit
73ab01a07df, from Jun 2016, so this is an old change.
Is this something that is worth fixing or is it something
all other MI consumers (but mine :-) are already used to so
it cannot be changed?
Best, Jan
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2018-10-10 9:39 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-10-10 9:39 =tsv-created MI event outputs extra "\n" on MI channel Jan Vrany
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).