From: Sandra Loosemore <sandra@codesourcery.com>
To: Tom Tromey <tom@tromey.com>, <gdb-patches@sourceware.org>
Subject: Re: [PATCH 3/3] Introduce a separate debug objfile iterator
Date: Tue, 30 Apr 2019 15:44:00 -0000 [thread overview]
Message-ID: <ee6c5cbc-8c0c-327c-6302-04b3c287f9ca@codesourcery.com> (raw)
In-Reply-To: <20190409180945.21621-4-tom@tromey.com>
On 4/9/19 12:09 PM, Tom Tromey wrote:
> This introduces a new iterator and range adapter for iteration over
> the separate debug files of a given objfile. As in the current
> approach, the requested objfile is returned first, followed by the
> separate debug objfiles.
>
> gdb/ChangeLog
> 2019-04-09 Tom Tromey <tom@tromey.com>
>
> * symtab.c (lookup_global_symbol_from_objfile)
> (lookup_symbol_in_objfile_from_linkage_name): Use the iterator.
> * objfiles.h (class separate_debug_iterator): New.
> (class separate_debug_range): New.
> (struct objfile) <separate_debug_objfiles>: New method.
> (objfile_separate_debug_iterate): Don't declare.
> * objfiles.c (separate_debug_iterator::operator++): Rename from
> objfile_separate_debug_iterate.
> (objfile_relocate, objfile_rebase, objfile_has_symbols): Use the
> iterator.
> * minsyms.c (lookup_minimal_symbol_by_pc_section): Use the
> iterator.
FYI, this series of patches has broken builds with older versions of GCC
(we've got 5.2.1 installed on our build system here). Multiple failures
like:
/path/to/gdb/minsyms.c: In function 'bound_minimal_symbol
lookup_minimal_symbol_by_pc_section(CORE_ADDR, obj_section*,
lookup_msym_prefer)':
/path/to/gdb/minsyms.c:724:8: error: types may not be defined in a
for-range-declaration [-Werror]
for (struct objfile *objfile :
section->objfile->separate_debug_objfiles ())
^~~~~~
-Sandra
next prev parent reply other threads:[~2019-04-30 15:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-09 18:11 [PATCH 0/3] some minor objfile iteration improvements Tom Tromey
2019-04-09 18:09 ` [PATCH 1/3] Remove some uses of "object_files" Tom Tromey
2019-04-10 1:49 ` Simon Marchi
2019-04-10 2:26 ` Tom Tromey
2019-04-10 2:50 ` Simon Marchi
2019-04-10 14:08 ` Tom Tromey
2019-04-09 18:09 ` [PATCH 2/3] Fix a couple of comments Tom Tromey
2019-04-10 1:51 ` Simon Marchi
2019-04-09 18:09 ` [PATCH 3/3] Introduce a separate debug objfile iterator Tom Tromey
2019-04-10 2:01 ` Simon Marchi
2019-04-10 14:08 ` Tom Tromey
2019-04-30 15:44 ` Sandra Loosemore [this message]
2019-04-30 15:51 ` Tom Tromey
2019-05-01 18:30 ` Tom Tromey
2019-05-03 18:23 ` Sandra Loosemore
2019-05-03 23:28 ` Tom Tromey
2019-05-15 9:45 ` John Marshall
2019-05-15 15:45 ` Tom Tromey
2019-05-15 20:00 ` John Marshall
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=ee6c5cbc-8c0c-327c-6302-04b3c287f9ca@codesourcery.com \
--to=sandra@codesourcery.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