Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Cc: palves@redhat.com, Iain Buclaw <ibuclaw@gdcproject.org>,
	Nick Alcock <nick.alcock@oracle.com>,
	Eli Zaretskii <eliz@gnu.org>
Subject: GDB 9.1 release -- 2020-01-17 update
Date: Fri, 17 Jan 2020 19:16:00 -0000	[thread overview]
Message-ID: <20200117185708.GJ4164@adacore.com> (raw)

Hi everyone,

I am hoping that we'll soon be able to push this one out the door!
We're getting closer, with one last minute addition that I think
we should indeed evaluate:

  - [IanB/PedroA] output out of order / issue with filtered/unfiltered output order
    https://sourceware.org/ml/gdb-patches/2019-11/msg00859.html

    Affects cgdb via annotations:
    https://sourceware.org/bugzilla/show_bug.cgi?id=25190

    Not sure if blocking or not, since there seems to be a workaround;
    or perhaps the workaround is OK for the annotations, but doesn't
    work so well for other situations?

Still Open:

  - [Eliz/NickA/JoelB] libtcf fails to build on MinGW
    https://sourceware.org/bugzilla/show_bug.cgi?id=25155

    The only issue left to fix is the issue with errno.
    Nick Alcock provided a prototype patch, and said he would
    inform us when the final patch is pushed. I privately sent
    a request for info earlier today.

Fixed Since the last update (2020-02-02):

  - [Andrew] unexpected disassembly output in backtrace
    https://sourceware.org/ml/gdb-patches/2019-12/msg01007.html

  - [Christian] Unable to build GDB on recent MinGW due to _FORTIFY_SOURCE
    https://sourceware.org/ml/gdb-patches/2019-12/msg00787.html

  - [Joel/Tom/Simon] Report error if trying to build GDB in tree
    https://www.sourceware.org/ml/gdb-patches/2020-01/msg00554.html
    https://www.sourceware.org/ml/gdb/2019-12/msg00034.html

-- 
Joel


             reply	other threads:[~2020-01-17 18:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-17 19:16 Joel Brobecker [this message]
2020-01-18  7:58 ` Iain Buclaw
2020-01-20 12:03 ` Nick Alcock

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=20200117185708.GJ4164@adacore.com \
    --to=brobecker@adacore.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=ibuclaw@gdcproject.org \
    --cc=nick.alcock@oracle.com \
    --cc=palves@redhat.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