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

Re: [PATCH] Fix MI output for multi-location breakpoints

From: Simon Marchi <simon dot marchi at ericsson dot com>
To: Andrew Burgess <andrew dot burgess at embecosm dot com>
Cc: Pedro Alves <palves at redhat dot com>, "gdb-patches at sourceware dot org" <gdb-patches at sourceware dot org>
Date: Sun, 13 Jan 2019 05:48:38 +0000
Subject: Re: [PATCH] Fix MI output for multi-location breakpoints
References: <20190111001516.4761-1-simon.marchi@ericsson.com> <20190111123420.GI3456@embecosm.com> <5cdbc81d-5198-f592-c142-8768991c306a@redhat.com> <973aa853-7a1b-4f7a-fd09-b99698aa6363@ericsson.com> <20190112014028.GK3456@embecosm.com>

On 2019-01-11 8:40 p.m., Andrew Burgess wrote:
> Do you think there's any benefit to adopting a more general solution
> to this issue?

I think that these are nice technical solutions, but now I fear the feature
creep in what started out as just fixing a simple bug :).

Perhaps something like that could be useful at some point, but for the moment
I don't think it's worth going through that much trouble and give that much
flexibility.  The reality is that stepping from MI2 to MI3 will be easy (at
least that's what I expect).

Simon

References:
- [PATCH] Fix MI output for multi-location breakpoints
  - From: Simon Marchi
- Re: [PATCH] Fix MI output for multi-location breakpoints
  - From: Andrew Burgess
- Re: [PATCH] Fix MI output for multi-location breakpoints
  - From: Pedro Alves
- Re: [PATCH] Fix MI output for multi-location breakpoints
  - From: Simon Marchi
- Re: [PATCH] Fix MI output for multi-location breakpoints
  - From: Andrew Burgess

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