[PATCH 1/3] MI: fix the result of -break-insert with multiple locations

Mircea Gherzan mircea.gherzan@intel.com
Thu Mar 7 16:32:00 GMT 2013


On 02.03.2013 17:53, André Pönitz wrote:
> On Thu, Feb 28, 2013 at 07:29:55PM +0100, Mircea Gherzan wrote:
>> The current MI output when printing a breakpoint with multiple locations
>> is not conformant to the MI specification:
>>
>>    bkpt={number="1", ...},{number="1.1", ...},{number="1.2", ...}
>>
>> This patch fixes this issue by moving the locations to a list inside the
>> first tuple:
>>
>>    bkpt={number="1", ... , locations=[{number="1.1", ...}, ...]}
>
> This breaks GDB frontends that parse the original output.

This has been discussed before. Marc has confirmed that Eclipse does not 
parse the original output either. With this patch series, the printing 
of breakpoints with multiple locations is:
   A) conformant to the MI syntax
   B) documented
   C) tested

With some review this should make it into 7.6.

Thanks,
Mircea

-- 

Intel GmbH
Dornacher Strasse 1
85622 Feldkirchen/Muenchen, Deutschland
Sitz der Gesellschaft: Feldkirchen bei Muenchen
Geschaeftsfuehrer: Christian Lamprechter, Hannes Schwaderer, Douglas Lusk
Registergericht: Muenchen HRB 47456
Ust.-IdNr./VAT Registration No.: DE129385895
Citibank Frankfurt a.M. (BLZ 502 109 00) 600119052



More information about the Gdb-patches mailing list