This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFC] Fix the MI result of -break-insert with multiple locations
- From: André Pönitz <andre dot poenitz at mathematik dot tu-chemnitz dot de>
- To: Mircea Gherzan <mircea dot gherzan at intel dot com>
- Cc: tromey at redhat dot com, vladimir at codesourcery dot com, marc dot khouzam at ericsson dot com, gdb-patches at sourceware dot org
- Date: Tue, 29 Jan 2013 20:45:20 +0100
- Subject: Re: [RFC] Fix the MI result of -break-insert with multiple locations
- References: <1359470164-32004-1-git-send-email-mircea.gherzan@intel.com>
On Tue, Jan 29, 2013 at 03:36:04PM +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 seems more like an additional burden for frontends which cannot
rely on a specific gdb version being installed as they have to keep
code to parse both results, for years.
The fact that the current output might not conform to the documented
grammar has no impact to existing frontends as they have/had to cope
with this kind of slight deviations anyway.
An alternative approach would be to just make the documentation match
the actual output. This is not unprecedented.
Andre'