public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: kevinb@redhat.com, scox@redhat.com, palves@redhat.com
Cc: gdb-patches@sourceware.org
Subject: GDB 8.2 release 2018-08-21 status update
Date: Tue, 21 Aug 2018 17:51:00 -0000	[thread overview]
Message-ID: <20180821175136.GA3365@adacore.com> (raw)

Hello,

We are now at nearly 7 weeks since we created the 8.1.90 pre-release.
This is a bit longer than the time we typically take to get the first
release out, but considering we're in the middle of the summer with
lots of us taking holidays (including myself), this is a bit to be
expected...

As you will see from below, there is potentially still a fair amount
of work to do :-/.

Here is the currently list of PRs we identified as blocking for 8.2:

  * [KevinB] PR gdb/23021
    Setting breakpoints with -freorder-blocks-and-partition
    https://sourceware.org/bugzilla/show_bug.cgi?id=23021

	Identified as needed in the previous release, but couldn't do it
        in time. We should be very close, now:
        [v3] https://sourceware.org/ml/gdb-patches/2018-08/msg00467.html

        I'm wondering how reasonable it's going to be to backport
        those changes onto the branch, though... Any thoughts on that?
        Kevin? Simon?

  * [KevinB] PR symtab/23010
    Regression: Assertion: SYMBOL_LANGUAGE (sym) == DICT_LANGUAGE (dict)->la_language
    https://sourceware.org/bugzilla/show_bug.cgi?id=23010

        This regression was seemingly fixed, and then makes a come back.
        I suggested we double-check this is indeed still a regression.

  * [StanC] PR varobj/23378
    gdb.mi/mi-var-cmd.exp, with gdbserver
    https://sourceware.org/bugzilla/show_bug.cgi?id=23378

        GDB not reporting that a variable is now out of scope
        (when in native GDBserver mode).

The following PRs are currently unassigned; Pedro's name was tentatively
put down, but only because he had the misfortune of being the reporter.
If possible, we should try to help Pedro finding the commit that caused
the regression -- I will take care of bisecting 23374 (a big Thank You
to Sergio DJ for helping with 23378).

  * [*UNASSIGNED* (Joel???)] PR gdb/23374
    gdb.base/execl-update-breakpoints.exp, with --target_board=native-gdbserver
    https://sourceware.org/bugzilla/show_bug.cgi?id=23374

        No problem with native debugging, or when using the native
        gdbserver in extended-remote mode.

  * [*UNASSIGNED* (Pedro???)] PR gdb/23375
    gdb.base/jit-simple.exp, with --target_board=native-gdbserver
    https://sourceware.org/bugzilla/show_bug.cgi?id=23375

        Same as above, native debugging and extended-remote OK.

  * [*UNASSIGNED* (Pedro???)] PR python/23379
    gdb.python/py-evthreads.exp, with gdbserver
    https://sourceware.org/bugzilla/show_bug.cgi?id=23379

        Internal error running to a breakpoint, when in native gdbserver
        mode. Pure native mode is OK.

Thanks!
-- 
Joel

             reply	other threads:[~2018-08-21 17:51 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-21 17:51 Joel Brobecker [this message]
2018-08-21 18:33 ` Kevin Buettner
2018-08-21 19:02 ` Simon Marchi
2018-08-21 20:17   ` Simon Marchi
2018-08-21 20:54     ` Joel Brobecker
2018-08-22 16:07       ` Simon Marchi
2018-08-22 17:38         ` Simon Marchi
2018-08-22 18:03         ` Stan Cox
2018-08-22 18:09           ` Simon Marchi
2018-08-21 20:55 ` Joel Brobecker
2018-08-21 21:29   ` Simon Marchi
2018-08-23 17:56     ` Pedro Alves
2018-08-24 18:01       ` Pedro Alves
2018-08-23 18:37 ` Simon Marchi
2018-08-23 22:41   ` Kevin Buettner
2018-08-24 18:35     ` Pedro Alves
2018-08-24 19:15       ` Simon Marchi
2018-08-24 19:52         ` Pedro Alves
2018-08-24  3:57 ` Kevin Buettner
2018-08-25  5:41   ` Kevin Buettner

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=20180821175136.GA3365@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=kevinb@redhat.com \
    --cc=palves@redhat.com \
    --cc=scox@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).