From: Tom Tromey <tromey@adacore.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/8] Add Ada support for .debug_names
Date: Wed, 31 Jul 2019 20:14:00 -0000 [thread overview]
Message-ID: <20190731201411.8044-1-tromey@adacore.com> (raw)
This series adds support for Ada in the .debug_names index.
This is mostly straightforward. The series starts with a few cleanup
patches, to make it simpler to share code with psymtabs.
While doing this I found two existing bugs.
One bug is fixed in patch #5, which includes a test case.
The other bug is more serious: gdb does not put the correct contents
into .debug_names. Fixing this would be very good, but it was not
something I wanted to do immediately. I've filed a bug with details:
https://sourceware.org/bugzilla/show_bug.cgi?id=24820
Regression tested on x86-64 Fedora 29.
Tom
next reply other threads:[~2019-07-31 20:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 20:14 Tom Tromey [this message]
2019-07-31 20:14 ` [PATCH 7/8] Add Ada support to cc-with-tweaks.exp Tom Tromey
2019-07-31 20:14 ` [PATCH 6/8] Add Ada support for .debug_names Tom Tromey
2019-07-31 20:14 ` [PATCH 2/8] Change iterate_over_symbols to return bool Tom Tromey
2019-07-31 20:14 ` [PATCH 1/8] Change map_matching_symbols to take a symbol_found_callback_ftype Tom Tromey
2019-07-31 20:14 ` [PATCH 3/8] Simplify psym_map_matching_symbols Tom Tromey
2019-07-31 20:14 ` [PATCH 8/8] Update "save gdb-index" documentation Tom Tromey
2019-08-01 2:36 ` Eli Zaretskii
2019-07-31 20:22 ` [PATCH 4/8] Change map_matching_symbols to take a lookup_name_info Tom Tromey
2019-07-31 20:22 ` [PATCH 5/8] Fix latent bug in .debug_names file-name handling Tom Tromey
2019-09-10 14:22 ` [PATCH 0/8] Add Ada support for .debug_names 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=20190731201411.8044-1-tromey@adacore.com \
--to=tromey@adacore.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