From: Tom Tromey <tom@tromey.com>
To: Tom de Vries <tdevries@suse.de>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [RFC][gdb/symtab] Lazy expansion of full symbol table
Date: Sun, 27 Jun 2021 16:24:06 -0600 [thread overview]
Message-ID: <87h7hjvtdl.fsf@tromey.com> (raw)
In-Reply-To: <25c649a5-6019-3500-7486-e909bac56f92@suse.de> (Tom de Vries's message of "Mon, 21 Jun 2021 11:18:33 +0200")
>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:
Tom> I managed to fix that using this patch:
Tom> ...
Tom> diff --git a/gdb/dwarf2/read.c b/gdb/dwarf2/read.c
Tom> index 265ebee1de8..f98acfa33ed 100644
Tom> --- a/gdb/dwarf2/read.c
Tom> +++ b/gdb/dwarf2/read.c
Tom> @@ -7204,7 +7204,8 @@ skip_one_die (const struct die_reader_specs
Tom> *reader, const gdb_b
Tom> yte *info_ptr,
Tom> /* We only handle DW_FORM_ref4 here. */
Tom> const gdb_byte *sibling_data = info_ptr + abbrev->sibling_offset;
Tom> unsigned int offset = read_4_bytes (abfd, sibling_data);
Tom> - const gdb_byte *sibling_ptr = buffer + offset;
Tom> + const gdb_byte *sibling_ptr
Tom> + = buffer + to_underlying (cu->header.sect_off) + offset;
Tom> if (sibling_ptr >= info_ptr && sibling_ptr < reader->buffer_end)
Tom> return sibling_ptr;
Tom> /* Fall through to the slow way. */
Tom> ...
Tom> The DW_FORM_ref4 offset is relative to the start of the CU, but buffer
Tom> points to the start of .debug_info.
Thanks. I think I copied this without realizing or remembering that
read_attribute_value adds in the section offset automatically.
Tom
next prev parent reply other threads:[~2021-06-27 22:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-14 9:39 Tom de Vries
2021-06-14 20:54 ` Tom Tromey
2021-06-14 23:36 ` Tom de Vries
2021-06-15 13:26 ` Tom Tromey
2021-06-16 10:20 ` Tom de Vries
2021-06-18 2:30 ` Tom Tromey
2021-06-19 19:36 ` Tom de Vries
2021-06-20 9:41 ` Tom de Vries
2021-06-20 18:17 ` Tom Tromey
2021-06-22 9:16 ` Tom de Vries
2021-06-20 23:44 ` Tom Tromey
2021-06-21 9:18 ` Tom de Vries
2021-06-27 22:24 ` Tom Tromey [this message]
2021-06-28 0:48 ` 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=87h7hjvtdl.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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