From: Edjunior Barbosa Machado <emachado@linux.vnet.ibm.com>
To: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: GDB 7.8 update (getting closer, new pre-release)
Date: Mon, 28 Jul 2014 20:20:00 -0000 [thread overview]
Message-ID: <53D6AF9E.8070205@linux.vnet.ibm.com> (raw)
In-Reply-To: <20140717133826.GL4888@adacore.com>
On 07/17/2014 10:38 AM, Joel Brobecker wrote:
> Hello everyone,
>
> First, a big Thank You to everyone who worked on cleaning out
> all the regressions and blocking issues so far. While the release
> process for this branch started as the quietest ever for me,
> the number of identified blocking issues eventually rose to about
> 3 times the number of issues identified in the previous release
> process. We're down to 3 entries in the TODO list before 7.8 release,
> so Thank You to everyone involved in the fixes getting us there.
>
> The 3 entries are:
>
> [Doug/Pedro] Asynchronous + all-stop problematic on gdbserver
> (being debated as not critical for 7.8, and I think I saw a patch
> from Doug to help the user in case of problem)
>
> [Doug] /usr/share/gdb/{guile,python}/ gets installed even --without-{guile,python}
> NTH - not serious, nice to have only
>
> [Doug] Precompile scheme files
> NTH - not critical, but just a bit more important than "nice to have"
>
> Issue #1 looks like it's on its way to being mitigated, and in
> the meantime isn't critical. Issue #2 is "nice to have", and
> issue #3 is "important".
>
> Doug - any thoughts on when we might a fix, at least for issue #3?
> I propose that we take issue #2 out of the mix. We've been doing
> this for Python files too, so it could be argued as not being
> a regression.
>
> I propose I make a second pre-release tomorrow morning, or even
> tonight. That should give people some time to re-test. I'm away
> next week, but hopefully by the time I come back, we'll be ready
> to make that release.
>
> Thoughts?
Hi,
is possible to check these 2 patches into 7.8 branch?
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=aebf9d247e4026189a0f612ee03c19cdf4bf86ac
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=572f65559b461133292118cee522b7e437714a07
These patches solve several unexpected failures from
gdb.base/watchpoint-reuse-slot.exp in ppc64 servers and s390/s390x due to
inappropriate handling on targets that don't support hw break/watchpoints.
Thanks,
--
Edjunior
next prev parent reply other threads:[~2014-07-28 20:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-17 13:39 Joel Brobecker
2014-07-17 15:07 ` H.J. Lu
2014-07-17 22:19 ` Joel Brobecker
[not found] ` <CAMe9rOp05O-S-Pg1cEiFm+FdzknDSwJg3FTrob-K=UPXKSMmEA@mail.gmail.com>
2014-07-20 0:56 ` Fwd: " Alan Modra
2014-07-28 18:18 ` Joel Brobecker
2014-07-28 19:04 ` H.J. Lu
2014-07-17 18:23 ` Doug Evans
2014-07-18 19:27 ` Doug Evans
2014-07-28 20:20 ` Edjunior Barbosa Machado [this message]
2014-07-28 20:23 ` Joel Brobecker
2014-07-28 21:47 ` Edjunior Barbosa Machado
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=53D6AF9E.8070205@linux.vnet.ibm.com \
--to=emachado@linux.vnet.ibm.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/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