From: Tom de Vries <tdevries@suse.de>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org, Simon Marchi <simon.marchi@polymtl.ca>
Subject: Re: [PATCH][gdb/symtab] Make gold index workaround more precise
Date: Tue, 26 May 2020 16:03:16 +0200 [thread overview]
Message-ID: <9219cd5c-f957-7879-c98b-5940c42704c0@suse.de> (raw)
In-Reply-To: <d91fb436-623d-34f9-fe8b-d5cf82575b0e@suse.de>
On 26-05-2020 15:01, Tom de Vries wrote:
> [ was: Re: [PATCH][gdb/symtab] Handle .gdb_index in ada language mode ]
> On 22-05-2020 22:31, Tom Tromey wrote:
>>>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:
>>
>> Tom> Using this patch, I managed to get it working.
>>
>> Wow, cool.
>>
>> Tom> The patch does the following:
>> Tom> - enable ada .gdb_index by removing the ada check in write_psymbols
>> Tom> - copy some ada-specific code from debug_names::insert to
>> Tom> write_psymbols
>> Tom> - disable a workaround for gold/15646 in dw2_expand_marked_cus
>>
>> Tom> As for the disabled workaround, I ran into trouble in
>> Tom> gdb.ada/access_tagged_param.exp, where setting a breakpoint on foo failed.
>>
>> Tom> The index shows that there are two entries for foo, one variable, one
>> Tom> function:
>> Tom> ...
>> Tom> [3733] foo:
>> Tom> 3 [global, variable]
>> Tom> 5 [global, function]
>> Tom> ...
>> Tom> The workaround skips the function, so disabling the workaround allows
>> Tom> the test to pass (my guess atm is that the workaround is not precise
>> Tom> enough).
>>
>> Looking at the gold bug, I suspect what's needed is to rule out
>> duplicates that have the same kind.
>>
>
> I've:
> - committed a target board gold-gdb-index
> - committed a test-case for the workaround
> (gdb.base/gold-gdb-index.exp), and
> - wrote a patch to make the duplicate check more precise (attached
> below).
>
> Any comments?
I tested this further in combination with the ada .gdb_index enabling,
and ran into failures in gdb.ada/bp_inlined_func.exp, which I managed to
fix by skipping the workaround when symbol_kind == function.
At this point, I wonder, should we just enable this workaround for
symbol_kind == type?
Thanks,
- Tom
next prev parent reply other threads:[~2020-05-26 14:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-13 9:41 [PATCH][gdb/symtab] Handle .gdb_index in ada language mode Tom de Vries
2020-05-19 20:32 ` Tom Tromey
2020-05-20 9:40 ` Tom de Vries
2020-05-22 20:31 ` Tom Tromey
2020-05-26 13:01 ` [PATCH][gdb/symtab] Make gold index workaround more precise Tom de Vries
2020-05-26 14:03 ` Tom de Vries [this message]
2020-05-27 15:22 ` Tom Tromey
2020-05-28 13:02 ` Tom de Vries
2020-05-27 15:21 ` Tom Tromey
2020-06-02 10:47 ` [PATCH][gdb/symtab] Handle .gdb_index in ada language mode Tom de Vries
2020-06-10 12:49 ` Tom de Vries
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=9219cd5c-f957-7879-c98b-5940c42704c0@suse.de \
--to=tdevries@suse.de \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
--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