From: Bernd Edlinger <bernd.edlinger@hotmail.de>
To: Simon Marchi <simon.marchi@polymtl.ca>,
Tom de Vries <tdevries@suse.de>,
gdb-patches@sourceware.org
Cc: Tom Tromey <tom@tromey.com>
Subject: Re: [PATCH][gdb/symtab] Handle DW_AT_ranges with DW_FORM_sec_off in partial DIE
Date: Tue, 26 Jan 2021 08:47:38 +0100 [thread overview]
Message-ID: <AM8PR10MB4708EB5073DDC7D4DAD8927DE4BC0@AM8PR10MB4708.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <b35fc0eb-b48d-d54c-6759-598af9e395ee@polymtl.ca>
On 1/26/21 2:52 AM, Simon Marchi wrote:
> On 2021-01-25 1:53 p.m., Bernd Edlinger wrote:
>> On 1/25/21 7:12 PM, Simon Marchi wrote:
>>>
>>>
>>> On 2021-01-25 12:42 p.m., Bernd Edlinger wrote:
>>>> On 1/25/21 5:36 PM, Simon Marchi wrote:
>>>>>> Yes, unfortunately I have not any experience with writing such assembly
>>>>>> tests, but I am always impressed when one of you does it though :-)
>>>>>>
>>>>>> Nevertheless, the test case seems to be stable from gcc-4.8 .. gcc-11,
>>>>>> that it fails without the patch and passes with the patch.
>>>>>>
>>>>>> So is it okay to push my partial symbols test as-is?
>>>>>
>>>>> My patch here adds a test that uses DW_FORM_sec_offset to point
>>>>> to a .debug_rnglists (DWARF5) section. Maybe that's sufficient,
>>>>> but if not I could probably do a DWARF4 equivalent.
>>>>>
>>>>> https://sourceware.org/pipermail/gdb-patches/2021-January/175229.html
>>>>>
>>>>
>>>> Yeah, the hardest part on a one-line change like this is always the test case.
>>>>
>>>> So, I tried this patch on current trunk, but it fails:
>>>>
>>>> Running /home/ed/gnu/gdb-build-1/gdb/testsuite/../../../binutils-gdb/gdb/testsuite/gdb.dwarf2/rnglists-multiple-cus.exp ...
>>>> ERROR: Couldn't load rnglists-multiple-cus-dw32 into GDB (GDB internal error).
>>>> ERROR: Couldn't load rnglists-multiple-cus-dw64 into GDB (GDB internal error).
>>>> Running /home/ed/gnu/gdb-build-1/gdb/testsuite/../../../binutils-gdb/gdb/testsuite/gdb.dwarf2/rnglists-sec-offset.exp ...
>>>> FAIL: gdb.dwarf2/rnglists-sec-offset.exp: is_64=false: p/x &foo
>>>> FAIL: gdb.dwarf2/rnglists-sec-offset.exp: is_64=true: p/x &foo
>>>>
>>>> This probably means that your test tests more than this single-line change alone?
>>>
>>> Hmm, with current master (so with Tom's patch merged),
>>> gdb.dwarf2/rnglists-sec-offset.exp passes for me.
>>>
>>
>> That will probably need investigation.
>> Let's first check if I applied the corrrect test case,
>> see attached patch.txt.
>
> It looks like the right patch (I looked at your second patch.txt).
>
Ah, sorry, my fault.
I have done the test with the wrong version,
now the test passes for me as well.
Bernd.
prev parent reply other threads:[~2021-01-26 7:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 12:24 Tom de Vries
2021-01-25 12:52 ` Bernd Edlinger
2021-01-25 15:27 ` Simon Marchi via Gdb-patches
2021-01-25 15:37 ` Tom de Vries
2021-01-25 15:47 ` Bernd Edlinger
2021-01-25 16:36 ` Simon Marchi via Gdb-patches
2021-01-25 17:42 ` Bernd Edlinger
2021-01-25 18:12 ` Simon Marchi via Gdb-patches
2021-01-25 18:53 ` Bernd Edlinger
2021-01-25 19:20 ` Bernd Edlinger
2021-01-26 1:52 ` Simon Marchi via Gdb-patches
2021-01-26 7:47 ` Bernd Edlinger [this message]
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=AM8PR10MB4708EB5073DDC7D4DAD8927DE4BC0@AM8PR10MB4708.EURPRD10.PROD.OUTLOOK.COM \
--to=bernd.edlinger@hotmail.de \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
--cc=tdevries@suse.de \
--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