From: Tom de Vries <tdevries@suse.de>
To: Tom Tromey <tom@tromey.com>, nitachra <Nitika.Achra@amd.com>
Cc: JiniSusan.George@amd.com, gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix for the complaint observed when symbol reading due to unsupported .debug_names form.
Date: Fri, 8 May 2020 16:36:19 +0200 [thread overview]
Message-ID: <43349381-fcbb-6e78-b4bc-9c15888ad260@suse.de> (raw)
In-Reply-To: <87k11nzxjn.fsf@tromey.com>
On 07-05-2020 15:26, Tom Tromey wrote:
>>>>>> ">" == nitachra <Nitika.Achra@amd.com> writes:
>
>>> Following complaint is observed with the executable compiled with -gdwarf-5
>>> and -gpubnames flags- "During symbol reading: Unsupported .debug_names form
>>> DW_FORM_ref4". This is the form corresponding to DW_IDX_die_offset attribute.
>>> This patch fixes this complaint. Tested with clang 10.0.0. Test case used-
>
>>> int main()
>>> {
>>> int sum,a,b;
>>> sum = a + b;
>>> return sum;
>>> }
>
> Does it fail some existing test in the gdb testsuite?
I don't think so, that is, not unless you use:
- clang as CC_FOR_TARGET, and
- target board unix/-gdwarf-5/-gpubnames.
> Normally what we like to see is either that a patch fixes some existing
> failure (perhaps when the test suite is run in a certain way); or a new
> test that fails before the patch and passes afterward.
>
I've add a dwarf assembly test-case for this (
https://sourceware.org/pipermail/gdb-patches/2020-May/168244.html ).
It should kfail without this patch, and pass with this patch (though it
doesn't pass for me on openSUSE due to the problem described in PR25941).
Thanks,
- Tom
next prev parent reply other threads:[~2020-05-08 14:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-04 6:13 nitachra
2020-05-07 13:26 ` Tom Tromey
2020-05-08 14:36 ` Tom de Vries [this message]
2020-05-08 15:16 ` Tom de Vries
2020-05-09 8:05 ` Tom de Vries
2020-05-11 17:50 nitachra
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=43349381-fcbb-6e78-b4bc-9c15888ad260@suse.de \
--to=tdevries@suse.de \
--cc=JiniSusan.George@amd.com \
--cc=Nitika.Achra@amd.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).