public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "zoran.zaric at amd dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug symtab/26813] DW_FORM_rnglistx and DW_FORM_loclistx not fully supported
Date: Fri, 30 Oct 2020 15:03:39 +0000 [thread overview]
Message-ID: <bug-26813-4717-Lujijr20or@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26813-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=26813
--- Comment #3 from Zoran Zaric <zoran.zaric at amd dot com> ---
Hi To,
I didn't want to contribute the patch per se, just wanted to try to speed up
the person who decides to take this on, with my quick understanding about what
is wrong.
If I had more time on my hands at the moment, I would contribute a real
solution with a gdb test included.
Unfortunately, that is not the case and my patch is not in a state to actually
be contributed.
If this is against the procedure, I don't mind if the patch is ignored.
It might not even be a correct solution anyway, considering that I didn't have
enough time to properly understand the bfd processing mechanism.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-10-30 15:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 17:30 [Bug symtab/26813] New: " zoran.zaric at amd dot com
2020-10-29 17:33 ` [Bug symtab/26813] " zoran.zaric at amd dot com
2020-10-29 18:08 ` simark at simark dot ca
2020-10-30 14:22 ` tromey at sourceware dot org
2020-10-30 15:03 ` zoran.zaric at amd dot com [this message]
2020-10-30 18:21 ` simark at simark dot ca
2020-10-30 18:22 ` simark at simark dot ca
2020-10-30 19:03 ` simark at simark dot ca
2020-10-30 21:19 ` simark at simark dot ca
2020-11-02 15:57 ` simark at simark dot ca
2021-01-20 9:26 ` mliska at suse dot cz
2021-02-02 15:42 ` cvs-commit at gcc dot gnu.org
2021-02-02 15:43 ` cvs-commit at gcc dot gnu.org
2021-02-02 15:43 ` cvs-commit at gcc dot gnu.org
2021-02-02 15:43 ` cvs-commit at gcc dot gnu.org
2021-02-02 15:43 ` simark at simark dot ca
2021-02-03 19:17 ` cvs-commit at gcc dot gnu.org
2021-02-03 19:17 ` cvs-commit at gcc dot gnu.org
2021-02-03 19:17 ` cvs-commit at gcc dot gnu.org
2022-05-15 12:13 ` jeanmichael.celerier at gmail dot com
2022-05-15 14:33 ` tromey at sourceware dot org
2022-05-15 14:55 ` jeanmichael.celerier at gmail dot com
2022-05-15 15:09 ` tromey at sourceware dot org
2022-05-16 1:12 ` simark at simark dot ca
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=bug-26813-4717-Lujijr20or@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.org \
/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).