From: Kevin Buettner <kevinb@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org, palves@redhat.com
Subject: Re: GDB 8.2 release 2018-08-21 status update
Date: Fri, 24 Aug 2018 03:57:00 -0000 [thread overview]
Message-ID: <20180823205718.3b941d0a@pinnacle.lan> (raw)
In-Reply-To: <20180821175136.GA3365@adacore.com>
On Tue, 21 Aug 2018 10:51:36 -0700
Joel Brobecker <brobecker@adacore.com> wrote:
> * [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?
I was able to apply the eight "non-contiguous address range support"
patches to my local checkout of gdb-8.2-branch. Part #2 needed some
fixing, but everything else applied cleanly (which kind of surprised
me).
I've tested on x86-64. No regressions.
Let me know if you want it pushed...
Kevin
next prev parent reply other threads:[~2018-08-24 3:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-21 17:51 Joel Brobecker
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 [this message]
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=20180823205718.3b941d0a@pinnacle.lan \
--to=kevinb@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--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