public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: time to release soon? GDB 8.1.1 release 2018-05-14 update
Date: Fri, 18 May 2018 19:14:00 -0000	[thread overview]
Message-ID: <20180518190017.7drpbrzmfg5h76pt@adacore.com> (raw)
In-Reply-To: <87r2ma2csw.fsf@tromey.com>

> Joel> Agreed that the second patch is a little invasive. Looking at the first
> Joel> one, it seems very localized, and can only affect Rust. If you feel
> Joel> confident that the patch is safe, we could just create a PR number
> Joel> for this issue, add it to the ChangeLog and revision log, and then
> Joel> use version #1 for the 8.1 branch.
> 
> If the DWARF reader patch goes in 8.1, then I will do that.
> Otherwise I probably won't.  I'm not very concerned about -readnow; I
> think pretty much only gdb developers use it or should use it.

OK with me. But wouldn't the issue surface as well without -readnow,
when expanding the partial symtab?

Regarding the DWARF reader patch, I'd say we put it in 8.1.1.
We haven't had any strong feedback on that question, but the feedback
we received so far has been more in favor of including it.  I don't
think the patch is so risky that it should be excluded (most of it
is purely mechanical); and since Sergio mentioned Fedora was going
to apply it, we might as well give it to everyone ;-). Worse case
scenario, if it causes problems, I can always do an emergency 8.1.2.

-- 
Joel

  reply	other threads:[~2018-05-18 19:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-14 17:59 Joel Brobecker
2018-05-17 16:19 ` Tom Tromey
2018-05-17 20:37   ` Joel Brobecker
2018-05-18  0:32     ` Tom Tromey
2018-05-18 19:14       ` Joel Brobecker [this message]
2018-05-18 19:50         ` Tom Tromey

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=20180518190017.7drpbrzmfg5h76pt@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.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).