public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: Joel Brobecker <brobecker@adacore.com>,
	gdb-patches@sourceware.org, Tom Tromey <tom@tromey.com>
Subject: Re: GDB 13 Release 2022-09-11 update
Date: Wed, 14 Sep 2022 17:58:37 +0200	[thread overview]
Message-ID: <1983cd06-68ec-e4e1-a2aa-200d016773bf@suse.de> (raw)
In-Reply-To: <Yx4oYEfEwXX/6ByZ@adacore.com>

On 9/11/22 20:26, Joel Brobecker via Gdb-patches wrote:
> Hi everyone,
> 
> We are now in September, and I think now is a good time to start
> working on our next major release.
> 
> Are there any issues we think should be fixed before we create
> the GDB 13 branch?
> 
> Looking at the PRs targetting 13.1 in bugzilla
> (https://sourceware.org/bugzilla/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=SUSPENDED&bug_status=WAITING&bug_status=REOPENED&list_id=24362&product=gdb&query_format=advanced&target_milestone=13.1)
> 
> ... I only see one "meta" bug related to TomT's new meta indexer.
> Do we have a list of known remaining issues that we need to fix?
> 

Perhaps it would be worth clarifying the status of support for .gdb_index.

It is the defacto standard for the index cache, but ada support is 
broken ( https://sourceware.org/bugzilla/show_bug.cgi?id=29179 ).

Do we want to fix this?

Do we want to deprecate .gdb_index and start using .debug_names for the 
index cache?

Or are we fine with the status quo (which then might need documenting)?

Thanks,
- Tom

  parent reply	other threads:[~2022-09-14 15:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-11 18:26 Joel Brobecker
2022-09-11 18:58 ` Philippe Waroquiers
2022-09-14 15:58 ` Tom de Vries [this message]
2022-09-15 22:41   ` Tom Tromey
2022-09-16 11:55     ` Tom de Vries
2022-09-19 23:26       ` Tom Tromey
2022-09-20  6:33         ` Tom de Vries

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=1983cd06-68ec-e4e1-a2aa-200d016773bf@suse.de \
    --to=tdevries@suse.de \
    --cc=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).