This is the mail archive of the gdb-prs@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]

[Bug mi/9659] -break-list can produce non MI compliant output


http://sourceware.org/bugzilla/show_bug.cgi?id=9659

Dimitar Zhekov <dimitar.zhekov at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dimitar.zhekov at gmail dot
                   |                            |com

--- Comment #2 from Dimitar Zhekov <dimitar.zhekov at gmail dot com> 2012-06-09 16:04:18 UTC ---
The bug is still present in 7.4.1. Additionally, multiply-location breakpoints
generate non-compliant output as well:

^done,BreakpointTable={nr_rows="2",nr_cols="6",hdr=[...],body=[bkpt={number="3",...},{number="3.1",...}]}

According to "GDB/MI Output Syntax", a list can (a) be empty, (b) contain
values or (c) contain results. But in the above output, body contains both
result and value.

The async break messages in 7.4+ have the same type of error:

=breakpoint-created,bkpt={number="3",...},{number="3.1",...}

contains both result and value, but async output may include results only.

In general, it's safer to assume that both list and tuple may contain a mix of
results and values. At this point, it may be better to change the
documentation...

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


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