This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: One month away from GDB 8.0 branching
- From: Antoine Tremblay <antoine dot tremblay at ericsson dot com>
- To: Joel Brobecker <brobecker at adacore dot com>
- Cc: Antoine Tremblay <antoine dot tremblay at ericsson dot com>, Yao Qi <qiyaoltc at gmail dot com>, "gdb-patches at sourceware dot org" <gdb-patches at sourceware dot org>, Tom Tromey <tom at tromey dot com>, Pedro Alves <palves at redhat dot com>, Andreas Arnez <arnez at linux dot vnet dot ibm dot com>
- Date: Sun, 19 Feb 2017 14:50:01 -0500
- Subject: Re: One month away from GDB 8.0 branching
- Authentication-results: sourceware.org; auth=none
- Authentication-results: spf=none (sender IP is ) smtp.mailfrom=antoine dot tremblay at ericsson dot com;
- References: <20170215035852.yzqw733mvnxigh2s@adacore.com> <wwok1suz7zm4.fsf@ericsson.com> <CAH=s-POY+MiTRg8sLGj01Ja+2Jz5HGOKprUETt2Er8dcgrN6aw@mail.gmail.com> <wwokino90ypq.fsf@ericsson.com> <20170219135317.cxlomg737l77h74g@adacore.com>
- Spamdiagnosticmetadata: NSPM
- Spamdiagnosticoutput: 1:99
Joel Brobecker writes:
>> 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.
Yes in light of your email about the blocking/non-blocking I'll discuss
that with Yao and Pedro. For my part and the users I know use this, it is
a likely issue... and there's no real workaround but to have a patched
GDB.
>
> 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.
Yes that one is a bit tricky, I'm on leave until April but it all
depends on what the way forward is and the complexity of the fix...
It's being discussed at least we'll see who can come up with the code
hopefully for 8.0.
Thanks!,
Antoine