From: Simon Marchi <simon.marchi@ericsson.com>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: Pedro Alves <palves@redhat.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Fix MI output for multi-location breakpoints
Date: Sun, 13 Jan 2019 05:49:00 -0000 [thread overview]
Message-ID: <5b9ba21c-9461-8f90-93de-7c5bc7b9c381@ericsson.com> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2019-01-13 5:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-11 0:15 Simon Marchi
2019-01-11 8:04 ` Eli Zaretskii
2019-01-11 20:21 ` Simon Marchi
[not found] ` <83y37qgail.fsf@gnu.org>
2019-01-12 17:01 ` Tom Tromey
2019-01-13 5:09 ` Simon Marchi
2019-01-13 15:32 ` Eli Zaretskii
2019-01-13 16:17 ` Simon Marchi
2019-01-13 16:49 ` Eli Zaretskii
2019-01-14 21:05 ` Simon Marchi
2019-01-11 12:34 ` Andrew Burgess
2019-01-11 18:39 ` Pedro Alves
2019-01-11 23:36 ` Simon Marchi
2019-01-12 1:40 ` Andrew Burgess
2019-01-12 16:54 ` Tom Tromey
2019-01-13 5:49 ` Simon Marchi [this message]
2019-01-11 21:07 ` Simon Marchi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5b9ba21c-9461-8f90-93de-7c5bc7b9c381@ericsson.com \
--to=simon.marchi@ericsson.com \
--cc=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox