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 8.0 branch created, now stabilizing...
Date: Mon, 17 Apr 2017 14:53:00 -0000	[thread overview]
Message-ID: <20170417145318.44k2i66luus3ojfy@adacore.com> (raw)

Hello,

I just created the gdb-8.0 branch from 725bf5cf125783c2a7ca4ab63d3768e220bab2db
(Sat Apr 15 00:00:36 2017 +0000), and updated the version numbers on
both that branch and master accordingly. Yay!

I haven't created the first pre-release, however, as I think we are
still waiting for the updates to the record & btrace Python APIs to
be included. It's better, IMO, to avoid sending out a pre-release
with an API that's going to change. Also, from what I've seen,
I think we're getting quite close to that work getting in.

In the meantime, the following issues are still open.

* server/21169  GDBServer on ARM can crash the inferior while single stepping

        Partial (but good-enough for the release) has been posted.
        URL?  Has there been an update since Apr 11th?

* build/21187 Static linking of libstdc++ and libgcc with GDB leads to broken exception handling on AIX platform

        Same update as a week ago: It looks like it stalled on
        the GCC side. Parallel to that, it seems like some people
        are working on a real fix on the compiler side, so perhaps
        we might not need a GDB patch after all?

        Also, some people indicated that we have the same issue
        on Windows (MinGW) and Darwin, but I had no such problem
        when I tried.

In the "maybe" category if someone finds the time:

* PR gdb/21356 (value_contents_bits_eq internal_error in value.c)

        Not strictly a regression, but an internal-error nonetheless,
        and perhaps fairly easy to fix (missing check_typedef???)

I'll try to send another update in a week or so. In the meantime,
please do not hesitate to reply to this message when some items
get completed. It really helps me track the various issues.

Thanks!
-- 
Joel


             reply	other threads:[~2017-04-17 14:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-17 14:53 Joel Brobecker [this message]
2017-04-17 16:39 ` Antoine Tremblay

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=20170417145318.44k2i66luus3ojfy@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