public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Luis Machado <luis.machado@arm.com>
To: Gustavo Romero <gustavo.romero@linaro.org>, gdb-patches@sourceware.org
Cc: thiago.bauermann@linaro.org, eliz@gnu.org, tom@tromey.com
Subject: Re: [PATCH v6 7/8] gdb/testsuite: Add unit tests for qIsAddressTagged packet
Date: Fri, 19 Apr 2024 15:31:39 +0100	[thread overview]
Message-ID: <9aa15f06-97ee-4273-ae03-28c930c5a246@arm.com> (raw)
In-Reply-To: <4693ce98-b5d5-bf2c-fd09-1ff97fd07092@linaro.org>

On 4/19/24 15:00, Gustavo Romero wrote:
> Hi Luis, Thiago, Eli, and Tom,
> 
> On 4/19/24 4:53 AM, Luis Machado wrote:
>> On 4/18/24 21:10, Gustavo Romero wrote:
>>> Add unit tests for testing qIsAddressTagged packet request creation and
>>> reply checks.
>>>
>>> Signed-off-by: Gustavo Romero <gustavo.romero@linaro.org>
>>> ---
>>>   gdb/remote.c | 67 ++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>   1 file changed, 67 insertions(+)
>>>
>>> diff --git a/gdb/remote.c b/gdb/remote.c
>>> index 3d034bb1ef8..cfb54de157d 100644
>>> --- a/gdb/remote.c
>>> +++ b/gdb/remote.c
>>> @@ -15682,6 +15682,8 @@ test_memory_tagging_functions ()
>>>     scoped_restore restore_memtag_support_
>>>       = make_scoped_restore (&config->support);
>>>   +  struct gdbarch *gdbarch = current_inferior ()->arch ();
>>> +
>>>     /* Test memory tagging packet support.  */
>>>     config->support = PACKET_SUPPORT_UNKNOWN;
>>>     SELF_CHECK (remote.supports_memory_tagging () == false);
>>> @@ -15748,6 +15750,71 @@ test_memory_tagging_functions ()
>>>     create_store_memtags_request (packet, 0xdeadbeef, 255, 1, tags);
>>>     SELF_CHECK (memcmp (packet.data (), expected.c_str (),
>>>                 expected.length ()) == 0);
>>> +
>>> +  /* Test creating a qIsAddressTagged request.  */
>>> +  expected = "qIsAddressTagged:deadbeef";
>>> +  create_is_address_tagged_request (gdbarch, packet, 0xdeadbeef);
>>> +  SELF_CHECK (strcmp (packet.data (), expected.c_str ()) == 0);
>>> +
>>> +  /* Test error reply on qIsAddressTagged request.  */
>>> +  reply = "E00";
>>> +  strcpy (packet.data (), reply.c_str ());
>>> +  /* is_tagged must not change, hence it's tested too.  */
>>> +  bool is_tagged = false;
>>> +  SELF_CHECK (check_is_address_tagged_reply (&remote, packet, is_tagged) ==
>>> +          false);
>>> +  SELF_CHECK (is_tagged == false);
>>> +
>>> +  /* Test 'tagged' as reply.  */
>>> +  reply = "01";
>>> +  strcpy (packet.data (), reply.c_str ());
>>> +  /* Because the byte is 01, is_tagged should be set to true.  */
>>> +  is_tagged = false;
>>> +  SELF_CHECK (check_is_address_tagged_reply (&remote, packet, is_tagged) ==
>>> +          true);
>>> +  SELF_CHECK (is_tagged == true);
>>> +
>>> +  /* Test 'not tagged' as reply.  */
>>> +  reply = "00";
>>> +  strcpy (packet.data (), reply.c_str ());
>>> +  /* Because the byte is 00, is_tagged should be set to false.  */
>>> +  is_tagged = true;
>>> +  SELF_CHECK (check_is_address_tagged_reply (&remote, packet, is_tagged) ==
>>> +          true);
>>> +  SELF_CHECK (is_tagged == false);
>>> +
>>> +  /* Test an invalid reply (neither 00 nor 01).  */
>>> +  reply = "04";
>>> +  strcpy (packet.data (), reply.c_str ());
>>> +  /* Because the byte is invalid is_tagged must not change.  */
>>> +  is_tagged = false;
>>> +  SELF_CHECK (check_is_address_tagged_reply (&remote, packet, is_tagged) ==
>>> +          false);
>>> +  SELF_CHECK (is_tagged == false);
>>> +
>>> +  /* Test malformed reply of incorrect length.  */
>>> +  reply = "0104A590001234006";
>>> +  strcpy (packet.data (), reply.c_str ());
>>> +  /* Because this is a malformed reply is_tagged must not change.  */
>>> +  is_tagged = false;
>>> +  SELF_CHECK (check_is_address_tagged_reply (&remote, packet, is_tagged) ==
>>> +          false);
>>> +  SELF_CHECK (is_tagged == false);
>>> +
>>> +  /* Test empty reply.  */
>>> +  reply = "";
>>> +  strcpy (packet.data (), reply.c_str ());
>>> +  /* is_tagged must not change, hence it's tested too.  */
>>> +  is_tagged = true;
>>> +  /* On the previous tests, qIsAddressTagged packet was auto detected and set
>>> +     as supported.  But an empty reply means the packet is unsupported, so for
>>> +     testing the empty reply the support is reset to unknown state, otherwise
>>> +     packet_ok will complain.   */
>>> +  remote.m_features.m_protocol_packets[PACKET_qIsAddressTagged].support =
>>> +    PACKET_SUPPORT_UNKNOWN;
>>> +  SELF_CHECK (check_is_address_tagged_reply (&remote, packet, is_tagged) ==
>>> +          false);
>>> +  SELF_CHECK (is_tagged == true);
>>>   }
>>>     static void
>>
>> This is OK. Thanks for the series.
>>
>> Let us know if you need us to push it for you.
>>
>> Approved-By: Luis Machado <luis.machado@arm.com>
>> Tested-By: Luis Machado <luis.machado@arm.com>
> 
> Thanks a lot for all the reviews!
> 
> Yip, I need somebody to push the patchset. :-)
> 
> 
> Cheers,
> Gustavo

Pushed now.

  reply	other threads:[~2024-04-19 14:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-18 20:10 [PATCH v6 0/8] Add another way to check tagged addresses on remote targets Gustavo Romero
2024-04-18 20:10 ` [PATCH v6 1/8] gdb: aarch64: Remove MTE address checking from get_memtag Gustavo Romero
2024-04-18 20:10 ` [PATCH v6 2/8] gdb: aarch64: Move MTE address check out of set_memtag Gustavo Romero
2024-04-18 20:10 ` [PATCH v6 3/8] gdb: aarch64: Remove MTE address checking from memtag_matches_p Gustavo Romero
2024-04-18 20:10 ` [PATCH v6 4/8] gdb: Use passed gdbarch instead of calling current_inferior Gustavo Romero
2024-04-18 20:10 ` [PATCH v6 5/8] gdb: Introduce is_address_tagged target hook Gustavo Romero
2024-04-18 20:10 ` [PATCH v6 6/8] gdb: Add qIsAddressTagged packet Gustavo Romero
2024-04-19  7:52   ` Luis Machado
2024-04-18 20:10 ` [PATCH v6 7/8] gdb/testsuite: Add unit tests for " Gustavo Romero
2024-04-19  7:53   ` Luis Machado
2024-04-19 14:00     ` Gustavo Romero
2024-04-19 14:31       ` Luis Machado [this message]
2024-04-18 20:10 ` [PATCH v6 8/8] gdb: Document " Gustavo Romero
2024-04-19  6:07   ` Eli Zaretskii

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=9aa15f06-97ee-4273-ae03-28c930c5a246@arm.com \
    --to=luis.machado@arm.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=gustavo.romero@linaro.org \
    --cc=thiago.bauermann@linaro.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).