public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
* [Bug mi/9166] malformed +download record on GNU ARM's arm-elf-gdb
       [not found] <bug-9166-4717@http.sourceware.org/bugzilla/>
@ 2015-09-25 21:03 ` matthijs at stdin dot nl
  0 siblings, 0 replies; only message in thread
From: matthijs at stdin dot nl @ 2015-09-25 21:03 UTC (permalink / raw)
  To: gdb-prs

https://sourceware.org/bugzilla/show_bug.cgi?id=9166

Matthijs Kooijman <matthijs at stdin dot nl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |matthijs at stdin dot nl

--- Comment #2 from Matthijs Kooijman <matthijs at stdin dot nl> ---
I just ran into this problem as well, so it is still present in gdb 7.6.0. Any
chance of fixing this?

As for the proposed fix, this would change from the invalid:

+download,{section=".vectors",section-size="60",total-size="5617"}

to a valid:

+download,status={section=".vectors",section-size="60",total-size="5617"}

It would probably be more consistent to instead just leave off the {}:

+download,section=".vectors",section-size="60",total-size="5617"

but I guess that would require changes to make_cleanup_ui_out_tuple_begin_end
to allow "top level tuples" or something like that.

For reference, here's an overview of the valid MI syntax:
https://sourceware.org/gdb/onlinedocs/gdb/GDB_002fMI-Output-Syntax.html#GDB_002fMI-Output-Syntax

-- 
You are receiving this mail because:
You are on the CC list for the bug.


^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2015-09-25 21:03 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <bug-9166-4717@http.sourceware.org/bugzilla/>
2015-09-25 21:03 ` [Bug mi/9166] malformed +download record on GNU ARM's arm-elf-gdb matthijs at stdin dot nl

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).