public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: Antoine Tremblay <antoine.tremblay@ericsson.com>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	Tom Tromey <tom@tromey.com>, Pedro Alves <palves@redhat.com>,
	Andreas Arnez <arnez@linux.vnet.ibm.com>
Subject: Re: One month away from GDB 8.0 branching
Date: Fri, 17 Feb 2017 10:12:00 -0000	[thread overview]
Message-ID: <20170217101157.4unltc3putfxtamj@adacore.com> (raw)
In-Reply-To: <CAH=s-POY+MiTRg8sLGj01Ja+2Jz5HGOKprUETt2Er8dcgrN6aw@mail.gmail.com>

> > I created a PR for this issue :
> > https://sourceware.org/bugzilla/show_bug.cgi?id=21169
> >
> > I've marked it Target Milestone 8.0
> >
> 
> I prefer to fixing this issue in 8.0 too, but to be clear, this is a
> 7.11 -> 7.12 regression.
> We changed GDBserver to single step over breakpoint on July 2016, but
> 7.12 was released on Oct 2016.

That's a very useful piece of information. Thanks, Yao.

Normally, the fact that this isn't a regression is a strong
indicator that we don't need to block a release pending resolution.
In this particular case, given the fairly bad effect on the debugging
session, and the fact that the regression was introduced in our last
branch, I propose a compromise. We leave it like that for now, and
will potentially delay the 8.0 release a bit waiting for the fix,
provided that some one is working on it, and tells us he is close
to having it. And, come release time, if we the fix is delayed
to much, or there isn't any news about it, we'll set change
the target milestone to 8.0.1 and try the same approach (wait a bit
if there are chances we might get the fix soon).

Does this sound OK?

-- 
Joel

  reply	other threads:[~2017-02-17 10:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-15  3:59 Joel Brobecker
2017-02-16  0:23 ` Antoine Tremblay
2017-02-16  9:05   ` Joel Brobecker
2017-02-16 12:42     ` Antoine Tremblay
2017-02-16 22:28   ` Yao Qi
2017-02-17 10:12     ` Joel Brobecker [this message]
2017-02-17 12:38       ` Antoine Tremblay
2017-02-19 13:48         ` Joel Brobecker
2017-02-19 19:43           ` Antoine Tremblay
2017-02-17 12:50     ` Antoine Tremblay
2017-02-19 13:53       ` Joel Brobecker
2017-02-19 19:50         ` Antoine Tremblay

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=20170217101157.4unltc3putfxtamj@adacore.com \
    --to=brobecker@adacore.com \
    --cc=antoine.tremblay@ericsson.com \
    --cc=arnez@linux.vnet.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --cc=qiyaoltc@gmail.com \
    --cc=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).