From: Joel Brobecker <brobecker@adacore.com>
To: Antoine Tremblay <antoine.tremblay@ericsson.com>
Cc: Yao Qi <qiyaoltc@gmail.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: Sun, 19 Feb 2017 13:53:00 -0000 [thread overview]
Message-ID: <20170219135317.cxlomg737l77h74g@adacore.com> (raw)
In-Reply-To: <wwokino90ypq.fsf@ericsson.com>
> Note however that the tests started failing when range-stepping got
> enabled, the change in July is the main issue but the range stepping
> introduced after 7.12 definetively made it worse to the point that the
> tests failed...
>
> So I would say it's a regression that got worse post 7.12...? Not sure
> how to classify that?
I would say that it depends on how often someone is likely to
hit the issue, and what the possible workarounds are.
More importantly, though, is anyone working on this issue as
we speak? For every blocking issue, there should be an assignee
who's taking charge of getting the issue fixed. Otherwise, we cannot
get updates on the issue, nor be sure that it'll get fixed in
a reasonable amount of time.
--
Joel
next prev parent reply other threads:[~2017-02-19 13:53 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
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 [this message]
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=20170219135317.cxlomg737l77h74g@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