public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Burgess <aburgess@redhat.com>
To: gdb-patches@sourceware.org
Cc: Andrew Burgess <aburgess@redhat.com>,
	Lancelot SIX <lsix@lancelotsix.com>, Tom Tromey <tom@tromey.com>
Subject: [PATCH 0/2] BFD cache management And Exec file with target: prefix
Date: Mon, 30 Oct 2023 13:41:21 +0000	[thread overview]
Message-ID: <cover.1698673143.git.aburgess@redhat.com> (raw)
In-Reply-To: <cover.1698246342.git.aburgess@redhat.com>

This started with patch #2, which improves GDB's handling of the main
executable having a target: prefix, but that ran into an issue with
the bfd cache.

So patch #1 aims to address this cache issue.

Changes in V2:

  - No longer using observers to call bfd_cache_close_all() (see V1
    discussion for reasons), instead I'm calling directly from core
    GDB after the before_prompt and target_resumed observers have been
    notified.

---

Andrew Burgess (2):
  gdb: move all bfd_cache_close_all calls in gdb_bfd.c
  gdb: fix reopen_exec_file for files with target: prefix

 gdb/corefile.c                                | 22 +++---
 gdb/event-top.c                               | 20 +++++-
 gdb/exec.c                                    |  2 -
 gdb/infcmd.c                                  |  1 -
 gdb/inferior.c                                |  2 -
 gdb/symfile.c                                 |  1 -
 gdb/target.c                                  |  5 --
 gdb/testsuite/gdb.server/target-exec-file.exp | 70 +++++++++++++++++++
 gdb/thread.c                                  |  5 ++
 9 files changed, 102 insertions(+), 26 deletions(-)


base-commit: 2029e13917d53d2289d3ebb390c4f40bd2112d21
-- 
2.25.4


  parent reply	other threads:[~2023-10-30 13:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-25 15:08 Andrew Burgess
2023-10-25 15:08 ` [PATCH 1/2] gdb: move all bfd_cache_close_all calls in gdb_bfd.c Andrew Burgess
2023-10-26  9:06   ` Lancelot SIX
2023-10-27  8:49     ` Andrew Burgess
2023-10-27 19:30   ` Tom Tromey
2023-10-30 10:20     ` Andrew Burgess
2023-10-31 18:28       ` Tom Tromey
2023-11-01 10:46         ` Andrew Burgess
2023-11-12 23:38           ` Tom Tromey
2023-10-25 15:08 ` [PATCH 2/2] gdb: fix reopen_exec_file for files with target: prefix Andrew Burgess
2023-10-27 18:39   ` Tom Tromey
2023-10-30 13:41 ` Andrew Burgess [this message]
2023-10-30 13:41   ` [PATCH 1/2] gdb: move all bfd_cache_close_all calls in gdb_bfd.c Andrew Burgess
2023-10-30 13:41   ` [PATCH 2/2] gdb: fix reopen_exec_file for files with target: prefix Andrew Burgess
2023-11-12 23:40   ` [PATCH 0/2] BFD cache management And Exec file " 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=cover.1698673143.git.aburgess@redhat.com \
    --to=aburgess@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=lsix@lancelotsix.com \
    --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).