Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: GDB <gdb-patches@sourceware.org>
Subject: Re: GDB 7.8 update (getting closer, new pre-release)
Date: Thu, 17 Jul 2014 15:07:00 -0000	[thread overview]
Message-ID: <CAMe9rOqNWg+JOt3-MBp8+N2j7n5vtft4i9uZNu+RJseUn7bLLw@mail.gmail.com> (raw)
In-Reply-To: <20140717133826.GL4888@adacore.com>

On Thu, Jul 17, 2014 at 6:38 AM, Joel Brobecker <brobecker@adacore.com> 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?
>

Is that possible to include those 2 patches:

https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=144bed8d4d8a1bdc0067f55f2ee71c07e5594677
https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=cca5b8b64b3286bb96cd7a2c18232d1acea85cd9

in GDB 7.8. It properly disassembles PLT section in libc.so with
IFUNC.

Thanks.

-- 
H.J.


  reply	other threads:[~2014-07-17 14:50 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 [this message]
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
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=CAMe9rOqNWg+JOt3-MBp8+N2j7n5vtft4i9uZNu+RJseUn7bLLw@mail.gmail.com \
    --to=hjl.tools@gmail.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