Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: GDB 10.1 release -- 2020-09-18 Update
Date: Fri, 18 Sep 2020 16:46:02 -0700	[thread overview]
Message-ID: <20200918234602.GA4674@adacore.com> (raw)

Hello,

A quick update on the release status since the 10.0.90 pre-release
was published last Saturday...

So far, we don't have anything really worrisome that could significantly
delay the release. I'll try to find some time to test the gnulib patches
that Eli pointed out next week.

Fixed Since the Previous Update:
--------------------------------

Fixed prior to branching:

  * [TomT/HannesD] <PR win32/25302>
    Mismatching fstat() function calls in gdb_bfd_open() and cache_bstat()
    https://sourceware.org/bugzilla/show_bug.cgi?id=25302

Fixed since branching:

  * [TomT] <PR gdb/26598> (reported by SimonM)
    skip compares pattern against mangled name
    https://sourceware.org/bugzilla/show_bug.cgi?id=26598

  * [TomT] <PR rust/26197>
    rust FAILs with rustc 1.36.0 and llvm 7
    https://sourceware.org/bugzilla/show_bug.cgi?id=26197

Added Since the Last Update:
----------------------------

Other Ongoing Items:
--------------------

  * [EliZ] <PR build/26607>
    GDB build failure in gnulib if building on Windows version older than 8
    https://sourceware.org/bugzilla/show_bug.cgi?id=26607

    gnulib pushed a couple of patches:
    https://sourceware.org/pipermail/gdb-patches/2020-September/171920.html

    The proposal is the following:
      - On the branch: we review, and test the two patches, then
        integrate them;
      - On master, we schedule a gnulib update.

Not Critical, but Requested:
----------------------------

  * [<unassigned>] <PR python/26586> (raised by Christian B)
    from_tty argument to Python's gdb.execute is no longer effective
    https://sourceware.org/bugzilla/show_bug.cgi?id=26586

    Not release blocking because not exactly a regressions (8.2 and 9
    already had the bug).

  * [AntonK, ShahabV] (suggested by SimonM)
    Add ARC Linux gdbserver support

    Patch (Aug 26th):
    https://sourceware.org/pipermail/gdb-patches/2020-August/171499.html

    Latest messages:
    https://sourceware.org/pipermail/gdb-patches/2020-September/171911.html

-- 
Joel


             reply	other threads:[~2020-09-18 23:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-18 23:46 Joel Brobecker [this message]
2020-09-19  1:37 ` Simon Marchi
2020-09-19 19:42   ` Joel Brobecker
2020-09-19 23:58     ` Simon Marchi
2020-09-19  7:41 ` Eli Zaretskii
2020-09-19 19:48   ` Joel Brobecker
2020-09-21 16:26     ` Eli Zaretskii
2020-09-26 17:39       ` Joel Brobecker
2020-09-28  9:30         ` Eli Zaretskii via Gdb-patches
2020-09-28 20:11           ` Joel Brobecker
2020-10-09 19:53             ` [pushed/gdb-10-branch] gnulib: fix stat/fstat build errors on old Windows version or using old MinGW Joel Brobecker
2020-09-20  1:03 ` GDB 10.1 release -- 2020-09-18 Update Simon Marchi
2020-09-20  6:09   ` Eli Zaretskii
2020-09-21 19:54 ` Simon Marchi
2020-09-23 13:39   ` Tom Tromey
2020-09-23 14:00     ` Simon Marchi

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=20200918234602.GA4674@adacore.com \
    --to=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