Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org, tom@tromey.com, sergiodj@redhat.com,
	yao.qi@arm.com
Subject: Re: GDB 8.1 branching 2017-12-04 update
Date: Sat, 09 Dec 2017 00:17:00 -0000	[thread overview]
Message-ID: <947684ba-ac4c-79e1-c10b-bd2258aaf111@redhat.com> (raw)
In-Reply-To: <20171204170202.lfukxwrqgzgbfxqm@adacore.com>

On 12/04/2017 05:02 PM, Joel Brobecker wrote:
>> One thing that I was thinking it'd be nice to see about getting
>> into 8.1 was the DWARF5 index stuff (standard replacement for 
>> .gdb_index):
>>
>>  https://sourceware.org/ml/gdb-patches/2017-05/msg00577.html
>>
>> Not sure about making that the default (seems risky), but it
>> might be nice to provide the option so that users/distros can
>> start experimenting (and so that Fedora/RHEL doesn't end up
>> having to backport yet another large series... :-P) .  I tried
>> to review that in the past but stumbled  on choices I didn't quite
>> understand, and there are also some open questions, but I was
>> planning on taking another look.  I can't really promise I/we can
>> get it done this week, so not sure about blocking the branching
>> because of it.
> 
> Indeed, it would be nice, and we can wait a bit to see if we manage
> to get it in. But looking at the size of the patch, unless you think
> it's almost ready and it's only a matter of a few fixes here and
> there, it seems like this might be a bit risky...
> 

I've played around with that series for a few days (on and off...),
and I've now pushed it in, with an important change that eliminates
most of the risk, IMO -- the original series made GDB default
to the new index format, while I left .gdb_index the default.
This should allow users/distros experimenting, and hopefully
any follow up fixes should be small/contained and easy to backport.

> Let's give ourselves this week, and see where we get. In the meantime,
> I've added this to the "maybe" section, before 18.1 branching.

Thanks,
Pedro Alves


  reply	other threads:[~2017-12-09  0:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-04 14:56 Joel Brobecker
2017-12-04 15:07 ` Tom Tromey
2017-12-04 15:21   ` Pedro Alves
2017-12-04 15:17 ` Pedro Alves
2017-12-04 17:02   ` Joel Brobecker
2017-12-09  0:17     ` Pedro Alves [this message]
2017-12-11  4:24       ` Joel Brobecker
2017-12-04 16:23 ` Yao Qi
2017-12-04 16:52   ` Joel Brobecker
2017-12-04 16:25 ` Pedro Alves
2017-12-04 17:11 ` Sergio Durigan Junior

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=947684ba-ac4c-79e1-c10b-bd2258aaf111@redhat.com \
    --to=palves@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=sergiodj@redhat.com \
    --cc=tom@tromey.com \
    --cc=yao.qi@arm.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