From: Bruno Larsen <blarsen@redhat.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: [PINGv7] [PATCH v4 0/2] [gdb] untie and validate inheritance location
Date: Mon, 20 Jun 2022 10:28:09 -0300 [thread overview]
Message-ID: <f4b9170c-06f8-ca6d-18da-382fdd063839@redhat.com> (raw)
In-Reply-To: <268cbb5d-b333-58d5-f78b-1c75779213e7@redhat.com>
ping!
Cheers!
Bruno Larsen
On 6/13/22 17:03, Bruno Larsen wrote:
> ping!
>
> Cheers!
> Bruno Larsen
>
> On 6/6/22 09:45, Bruno Larsen wrote:
>> ping!
>>
>> Cheers!
>> Bruno Larsen
>>
>> On 5/30/22 08:15, Bruno Larsen wrote:
>>> ping
>>>
>>> Cheers!
>>> Bruno Larsen
>>>
>>> On 5/24/22 08:26, Bruno Larsen wrote:
>>>> ping
>>>>
>>>> Cheers!
>>>> Bruno Larsen
>>>>
>>>> On 5/18/22 08:24, Bruno Larsen wrote:
>>>>> ping
>>>>>
>>>>> Cheers!
>>>>> Bruno Larsen
>>>>>
>>>>> On 5/11/22 08:12, Bruno Larsen wrote:
>>>>>> Ping
>>>>>>
>>>>>> Cheers!
>>>>>> Bruno Larsen
>>>>>>
>>>>>> On 4/27/22 09:28, Bruno Larsen wrote:
>>>>>>> Changelog for v4:
>>>>>>> * rebased on master
>>>>>>> * removed unnecessary checking after Simon's patch
>>>>>>>
>>>>>>> This started with what was thought of as an incorrect inheritance
>>>>>>> location expression, but turned out to be a correct, but unusual
>>>>>>> expression, and uncovered an incorrect assumption when calculating
>>>>>>> offsets of baseclasses.
>>>>>>>
>>>>>>> This patchset is the new iteration of that solution, that changed
>>>>>>> gnuv3_baseclass_offset calculation to allow for non-virtual inheritance
>>>>>>> that has a non-trivial location expression and also moved the basic
>>>>>>> validation to this function. The check in value_contents_copy_raw was
>>>>>>> changed to an assert.
>>>>>>> Finally, the test was expanded to have one incorrect trivial location,
>>>>>>> and two non-trivial location expressions, one correct and one incorrect.
>>>>>>>
>>>>>>> Bruno Larsen (2):
>>>>>>> [gdb] Untied inheritance virtuality and loc kind
>>>>>>> [gdb] Add Simple offset validation when calculating baseclass_offset
>>>>>>>
>>>>>>> gdb/gnu-v3-abi.c | 24 +-
>>>>>>> .../gdb.dwarf2/dw2-inheritance-locexpr-1.exp | 233 +++++++++++++++++
>>>>>>> .../gdb.dwarf2/dw2-inheritance-locexpr-2.exp | 235 ++++++++++++++++++
>>>>>>> .../gdb.dwarf2/dw2-inheritance-locexpr.c | 69 +++++
>>>>>>> gdb/value.c | 8 +-
>>>>>>> 5 files changed, 562 insertions(+), 7 deletions(-)
>>>>>>> create mode 100644 gdb/testsuite/gdb.dwarf2/dw2-inheritance-locexpr-1.exp
>>>>>>> create mode 100644 gdb/testsuite/gdb.dwarf2/dw2-inheritance-locexpr-2.exp
>>>>>>> create mode 100644 gdb/testsuite/gdb.dwarf2/dw2-inheritance-locexpr.c
>>>>>>>
next prev parent reply other threads:[~2022-06-20 13:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 12:28 Bruno Larsen
2022-04-27 12:28 ` [PATCH v4 1/2] [gdb] Untied inheritance virtuality and loc kind Bruno Larsen
2022-04-27 12:28 ` [PATCH v4 2/2] [gdb] Add Simple offset validation when calculating baseclass_offset Bruno Larsen
2022-05-11 11:12 ` [PING] [PATCH v4 0/2] [gdb] untie and validate inheritance location Bruno Larsen
2022-05-18 11:24 ` [PINGv2] " Bruno Larsen
2022-05-24 11:26 ` [PINGv3] " Bruno Larsen
2022-05-30 11:15 ` [PINGv4] " Bruno Larsen
2022-06-06 12:45 ` [PINGv5] " Bruno Larsen
2022-06-13 20:03 ` [PINGv6] " Bruno Larsen
2022-06-20 13:28 ` Bruno Larsen [this message]
2022-06-27 11:24 ` [PINGv8] " Bruno Larsen
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=f4b9170c-06f8-ca6d-18da-382fdd063839@redhat.com \
--to=blarsen@redhat.com \
--cc=gdb-patches@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).