This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 1/3] MI: fix the 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, mgherzan at gmail dot com
- Date: Thu, 7 Mar 2013 21:53:51 +0100
- Subject: Re: [PATCH 1/3] MI: fix the result of -break-insert with multiple locations
- References: <1362076197-15363-1-git-send-email-mircea.gherzan@intel.com> <20130302165337.GA8432@klara.mpi.htwm.de> <5138C0F7.6060703@intel.com>
On Thu, Mar 07, 2013 at 05:31:51PM +0100, Mircea Gherzan wrote:
> 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.
As in "we ignored your input".
> Marc has confirmed that Eclipse does not parse the original output either.
How does the non-affectedness of a specific frontend matter
in that context? Are there first and second class citizens
when it comes to gdb frontends?
This breaks frontends that parses the original output and do
(obviously...) not understand your changed version.
Have fun.
Andre'