GDB 7.12 release - 2016-09-21 update?

[Joel Brobecker <brobecker at adacore dot com>]

Hello everyone,

Sorry for being radio-silent the last few weeks. It's been a combination
of a crazy traveling schedule, and that thing we call "work"...

Anyways, I reviewed the list of PRs marked as targetting 7.12,
as well as the items listed in our 7.12 release page
(https://sourceware.org/gdb/wiki/GDB_7.12_Release).

It looks like we may have a ways to go before being able to release.
Here are my thoughts on each of them. What do you guys think?

PR 20395: -var-update gives incorrect register values for frames 1 and above

        Assigned to: Don Breazeal
        Status: Patch proposed, but not sure it is good.

        Proposed as blocker for 7.12 because incorrect data is returned.
        However, not sure whether I agree or not yet. I think a better
        question to ask would be: Is it a regression compared to 7.11?

PR 20448: target descriptions: bitfields vs flags backward/forward incompatible change

        Assigned to: *** UNASSIGNED ***
        Status: ???

        This is an actual regression, so I agree we should try to get
        this fixed for 7.12.

        Is anyone working on this?

PR 20627: GDBserver can not be closed

        Assigned to: *** UNASSIGNED ***
        Status: ???

        Not sure if this is a regression or not, and whether it is
        actually critical for 7.12. If there is no data loss, perhaps
        we can just document the workaround.

        Yao?

PR 20487: Thread sync broken between mi and cli with new-ui command

        Assigned to: Antoine Tremblay
        Status: Fix in progress

        Not sure if this is really blocking for 7.12 either as it
        relates to a new feature. But since we seem to be close to
        a resolution, and this makes the new feature more usable,
        perhaps we can try to have it in 7.12. Otherwise, perhaps
        release 7.12 with this limitation in the release notes,
        and fix it for 7.12.1???

PR 11094: cannot reexecute programs using the GDB JIT interface in shared libs

        Assigned to: Pedro Alves
        Status: Fix posted.

        I don't think it's the reported issue itself that was the cause
        of making this PR blocking for 7.12, but rather the SEGV that
        was detected after the patch was pushed in. The fix was posted,
        so I suspect we can have a quick resolution for this one.

PR 20609 gdb --pid $(pidof qemu-system-x86_64) stopped working with gdb 7.11.1

        Assigned to: *** UNASSIGNED ***
        Status: ???

        As hinted by the subject, this is a real regression, and
        the problem description says that this leads to a non-functional
        session.

        Is anyone working on this?

Thanks!
-- 
Joel