public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Cc: Pedro Alves <palves@redhat.com>,
	macro@linux-mips.org, tom@tromey.com,	simon.marchi@ericsson.com
Subject: GDB 8.1 release -- 2018-01-08 update
Date: Mon, 08 Jan 2018 07:49:00 -0000	[thread overview]
Message-ID: <20180108074937.fq44jr4qkdphgeew@adacore.com> (raw)

Hello,

The gdb-8.1-branch was created last Friday :).

Here is the list of issues identified as blocking for 8.1 release:

  * [Pedro] gdb/22583
    gdb.base/breakpoint-in-ro-region.exp regressions on software
    single-step tar gets

  * [Maciej] remote/22597
    Empty `qsThreadInfo' reply handling regression causing inability to execute

    I'm trying to understand whether this is specific to mips or more
    general. And whether this only affects GDB when debugging with older
    stubs or whether it affects us more generally.

    Depending on the answer, the issue might not be so severe as
    to hold the release.

    Maciej - can you tell where we are on this issue, and whether
    you think it really is blocking for 8.1?

  * [Pedro/Joel] gdb/22670
    regressions in Ada caused by introduction of wild matching in
    C++ patch series

    Pedro has a fix for all the issues identified so far.
    On my end, I have gone through most of the failures I see
    using the AdaCore testsuite, with 5 left to go. Intuitively,
    I think we're through, but I'll have confirmation by end of
    this week.

  * [TomT] no PR yet
    Regression on 32-bit: gdb.guile/scm-ports.exp [Re: [RFA 1/2]
    Fix two regress ions in scalar printing
    https://sourceware.org/ml/gdb-patches/2017-12/msg00215.html

    Tom posted a patch which was recently approved. So it's a matter
    of pushing it, and backporting it.

  * [SimonM] no PR yet
    hurd: Add enough auxv support for AT_ENTRY for PIE binaries

    Patch looks good to Simon. Just needs to be pushed, or else
    backported if not pushed before branching.

    Any progress on this patch?

Looking at the list, once we close gdb/22670, I think we can
make our first pre-release, but please let me know if you believe
some of those issues above are critical enough that a pre-release
would not be useful yet.

Thanks!
-- 
Joel

             reply	other threads:[~2018-01-08  7:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-08  7:49 Joel Brobecker [this message]
2018-01-08  9:55 ` Maciej W. Rozycki
2018-01-08 16:35   ` Pedro Alves
2018-01-08 17:00     ` Maciej W. Rozycki
2018-01-09  1:28     ` [PATCH] Fix backwards compatibility with old GDBservers (PR remote/22597) (Re: GDB 8.1 release -- 2018-01-08 update) Pedro Alves
2018-01-10 11:18       ` Maciej W. Rozycki
2018-01-11  0:36         ` Pedro Alves
2018-01-08 15:50 ` GDB 8.1 release -- 2018-01-08 update Simon Marchi
2018-01-08 15:53 ` Tom Tromey

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=20180108074937.fq44jr4qkdphgeew@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=macro@linux-mips.org \
    --cc=palves@redhat.com \
    --cc=simon.marchi@ericsson.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).