From: Aaron Merey <amerey@redhat.com>
To: gdb-patches@sourceware.org
Cc: aburgess@redhat.com, Aaron Merey <amerey@redhat.com>
Subject: [PATCH 0/3] On-demand debuginfo downloading
Date: Fri, 3 May 2024 18:58:59 -0400 [thread overview]
Message-ID: <20240503225902.2866347-1-amerey@redhat.com> (raw)
Patch set that adds support for lazy/on-demand downloading of debuginfo
as well as .gdb_index, .debug_line and .debug_line_str ELF section
downloading.
Patches 1 and 3 are reposts with no changes. Patch 2 has a couple minor
changes based on Andrew's review:
https://sourceware.org/pipermail/gdb-patches/2024-March/207593.html
Aaron Merey (3):
gdb/progspace: Add reverse safe iterator
gdb/debuginfod: Support on-demand debuginfo downloading
gdb/debuginfod: Add .debug_line downloading
gdb/cli-out.c | 11 +-
gdb/completer.c | 18 +-
gdb/dwarf2/frame.c | 13 +
gdb/dwarf2/frame.h | 4 +
gdb/dwarf2/index-cache.c | 22 +-
gdb/dwarf2/index-cache.h | 11 +
gdb/dwarf2/line-header.c | 161 +++++++---
gdb/dwarf2/line-header.h | 10 +
gdb/dwarf2/public.h | 5 +
gdb/dwarf2/read-gdb-index.c | 183 ++++++++++-
gdb/dwarf2/read.c | 357 ++++++++++++++++++++-
gdb/dwarf2/read.h | 47 +++
gdb/dwarf2/section.c | 3 +-
gdb/elfread.c | 3 +-
gdb/frame.c | 27 +-
gdb/jit.c | 7 +-
gdb/mi/mi-out.c | 9 +-
gdb/objfile-flags.h | 4 +
gdb/objfiles.c | 14 +-
gdb/objfiles.h | 37 ++-
gdb/progspace.c | 19 +-
gdb/progspace.h | 31 +-
gdb/quick-symbol.h | 4 +
gdb/symfile-debug.c | 45 ++-
gdb/symfile.c | 12 +-
gdb/symtab.c | 18 +-
gdb/testsuite/gdb.debuginfod/libsection1.c | 43 +++
gdb/testsuite/gdb.debuginfod/libsection2.c | 37 +++
gdb/testsuite/gdb.debuginfod/section.c | 29 ++
gdb/testsuite/gdb.debuginfod/section.exp | 184 +++++++++++
gdb/testsuite/gdb.python/py-objfile.exp | 2 +-
gdb/testsuite/lib/debuginfod-support.exp | 25 +-
gdb/testsuite/lib/gdb.exp | 8 +-
gdb/ui-out.c | 3 +
gdb/ui-out.h | 20 ++
gdbsupport/safe-iterator.h | 115 +++++++
36 files changed, 1408 insertions(+), 133 deletions(-)
create mode 100644 gdb/testsuite/gdb.debuginfod/libsection1.c
create mode 100644 gdb/testsuite/gdb.debuginfod/libsection2.c
create mode 100644 gdb/testsuite/gdb.debuginfod/section.c
create mode 100644 gdb/testsuite/gdb.debuginfod/section.exp
--
2.43.0
next reply other threads:[~2024-05-03 22:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 22:58 Aaron Merey [this message]
2024-05-03 22:59 ` [PATCH 1/3 v3] gdb/progspace: Add reverse safe iterator Aaron Merey
2024-05-17 14:09 ` [PING][PATCH " Aaron Merey
2024-05-31 20:58 ` [PING*2][PATCH " Aaron Merey
2024-06-07 20:48 ` [PING*3][PATCH " Aaron Merey
2024-06-14 18:23 ` [PING*2][PATCH " Aaron Merey
2024-05-03 22:59 ` [PATCH 2/3 v6] gdb/debuginfod: Support on-demand debuginfo downloading Aaron Merey
2024-05-17 14:10 ` [PING][PATCH " Aaron Merey
2024-05-31 20:58 ` [PING*2][PATCH " Aaron Merey
2024-06-07 20:48 ` [PING*3][PATCH " Aaron Merey
2024-06-14 18:24 ` Aaron Merey
2024-06-17 10:45 ` [PATCH " Andrew Burgess
2024-06-17 19:57 ` Aaron Merey
2024-05-03 22:59 ` [PATCH 3/3 v6] gdb/debuginfod: Add .debug_line downloading Aaron Merey
2024-05-17 14:10 ` [PING][PATCH " Aaron Merey
2024-05-31 20:58 ` [PING*2][PATCH " Aaron Merey
2024-06-07 20:49 ` [PING*3][PATCH " Aaron Merey
2024-06-14 18:24 ` Aaron Merey
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=20240503225902.2866347-1-amerey@redhat.com \
--to=amerey@redhat.com \
--cc=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
/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).