From: Simon Marchi <simon.marchi@ericsson.com>
To: <gdb-patches@sourceware.org>
Cc: Simon Marchi <simon.marchi@ericsson.com>
Subject: [PATCH RFC 0/5] Add a DWARF index cache
Date: Wed, 09 May 2018 21:57:00 -0000 [thread overview]
Message-ID: <1525901216-15031-1-git-send-email-simon.marchi@ericsson.com> (raw)
Message-ID: <20180509215700.IXcrGj-G55WKRITHZhRimUEkEca7UdGX1v9fXk-cENQ@z> (raw)
I made a quick and dirty prototype a while ago where GDB would automatically
save and lookup DWARF index files. A few people told me that it was quite
useful, so I'm trying to make it suitable for merging. I'm sending it as an
RFC first to get comments on the feature and the approach, and because there
are probably a few loose ends. Patches 1-4 are mostly cleanup or preparatory,
the final one contains the actual feature. The commit message of that last
patch also contains more details.
Simon Marchi (5):
Rename some functions, index -> gdb_index
Remove mapped_index::total_size
Make index reading functions more modular
Introduce scoped_mmapped_file
Add DWARF index cache
gdb/Makefile.in | 3 +
gdb/build-id.h | 11 +
gdb/common/pathstuff.c | 16 +
gdb/common/pathstuff.h | 10 +
gdb/common/scoped_fd.h | 17 +-
gdb/common/scoped_mmapped_file.h | 70 +++++
gdb/dwarf-index-cache.c | 421 ++++++++++++++++++++++++++
gdb/dwarf-index-cache.h | 86 ++++++
gdb/dwarf-index-common.h | 5 +
gdb/dwarf-index-write.c | 81 +++--
gdb/dwarf-index-write.h | 34 +++
gdb/dwarf2read.c | 257 +++++++++++-----
gdb/dwarf2read.h | 5 +
gdb/testsuite/boards/local-board.exp | 1 +
gdb/testsuite/gdb.base/index-cache.c | 23 ++
gdb/testsuite/gdb.base/index-cache.exp | 204 +++++++++++++
gdb/testsuite/gdb.base/maint.exp | 23 ++
gdb/testsuite/lib/mi-support.exp | 16 +-
gdb/unittests/scoped_mmapped_file-selftests.c | 95 ++++++
19 files changed, 1270 insertions(+), 108 deletions(-)
create mode 100644 gdb/common/scoped_mmapped_file.h
create mode 100644 gdb/dwarf-index-cache.c
create mode 100644 gdb/dwarf-index-cache.h
create mode 100644 gdb/dwarf-index-write.h
create mode 100644 gdb/testsuite/gdb.base/index-cache.c
create mode 100644 gdb/testsuite/gdb.base/index-cache.exp
create mode 100644 gdb/unittests/scoped_mmapped_file-selftests.c
--
2.7.4
next reply other threads:[~2018-05-09 21:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-09 21:27 Simon Marchi [this message]
2018-05-09 21:27 ` [PATCH RFC 1/5] Rename some functions, index -> gdb_index Simon Marchi
2018-05-10 20:40 ` Tom Tromey
2018-06-12 2:03 ` Simon Marchi
2018-05-09 21:27 ` [PATCH RFC 2/5] Remove mapped_index::total_size Simon Marchi
2018-05-09 23:08 ` Simon Marchi
2018-05-10 20:54 ` Tom Tromey
2018-05-18 20:26 ` Simon Marchi
2018-05-09 21:27 ` [PATCH RFC 3/5] Make index reading functions more modular Simon Marchi
2018-05-10 21:02 ` Tom Tromey
2018-05-10 21:18 ` Simon Marchi
2018-05-09 21:27 ` [PATCH RFC 5/5] Add DWARF index cache Simon Marchi
2018-05-10 22:24 ` Tom Tromey
2018-07-09 20:56 ` Simon Marchi
2018-05-09 21:27 ` [PATCH RFC 4/5] Introduce scoped_mmapped_file Simon Marchi
2018-05-10 21:04 ` Tom Tromey
2018-05-10 21:27 ` Simon Marchi
2018-05-12 15:49 ` Tom Tromey
2018-06-13 1:36 ` Simon Marchi
2018-05-09 21:57 ` [PATCH RFC 0/5] Add a DWARF index cache Simon Marchi
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=1525901216-15031-1-git-send-email-simon.marchi@ericsson.com \
--to=simon.marchi@ericsson.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).