Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Wei-cheng Wang <cole945@gmail.com>
To: Yao Qi <yao@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix memory-region overlapping checking
Date: Thu, 16 Aug 2012 10:03:00 -0000	[thread overview]
Message-ID: <CAPmZyH4tJS=DyhL+3eJFkG=1yD5ttXS5t7=ffzgK6PGKcxmBrA@mail.gmail.com> (raw)
In-Reply-To: <1450628.xUgDUToN8c@qiyao.dyndns.org>

Hi Yao,

  Thanks for your correction.
  I wasn't aware of that rule and wondered what the message is used for.

  After I reviewed the cases, I think the cases should be altered a little.
  When testing against 0x30-0x0, 0x50-0x70 is no different than 0x40-0x50,
  so I remove it and add various boundary cases.

  Below is the altered one based on your fix.

--
Wei-cheng


2012-08-08  Wei-cheng Wang  <cole945@gmail.com>
	    Yao Qi <yao@codesourcery.com>

	* gdb.base/memattr.exp: Add cases for overlapping checking.

diff --git INDEX:/gdb/testsuite/gdb.base/memattr.exp
--- INDEX:/gdb/testsuite/gdb.base/memattr.exp
+++ WORKDIR:/gdb/testsuite/gdb.base/memattr.exp
@@ -448,3 +448,45 @@ gdb_test_multiple "info mem" "mem 2-4 were deleted" {

 gdb_test "delete mem 8" "No memory region number 8." \
     "delete non-existant region"
+
+#
+# Test overlapping checking
+#
+#       lo'        hi'
+#        |---------|
+#  10 20 30 40 50 60 70 80
+#      |----|             FAIL
+#        |--|             FAIL
+#           |---|         FAIL
+#               |--|      FAIL
+#               |----|    FAIL
+#        |---------|      FAIL
+#      |-------------|    FAIL
+#      |----------------- FAIL
+#           |------------ FAIL
+#                    |--- FAIL
+#   |----|                PASS
+#                  |----| PASS
+
+proc delete_memory {} {
+    global gdb_prompt
+
+    gdb_test_multiple "delete mem" "delete mem" {
+       -re "Delete all memory regions.*y or n.*$" {
+           send_gdb "y\n";
+           exp_continue
+       }
+       -re "$gdb_prompt $" { }
+    }
+}
+
+# Test normal case (upper != 0)
+delete_memory
+gdb_test_no_output "mem 0x30 0x60 ro"
+gdb_test "mem 0x20 0x40 ro" "overlapping memory region" "mem 0x20 0x40 1"
+gdb_test "mem 0x30 0x40 ro" "overlapping memory region" "mem 0x30 0x40 1"
+gdb_test "mem 0x40 0x50 ro" "overlapping memory region" "mem 0x40 0x50 1"
+gdb_test "mem 0x50 0x60 ro" "overlapping memory region" "mem 0x50 0x60 1"
+gdb_test "mem 0x30 0x60 ro" "overlapping memory region" "mem 0x30 0x60 1"
+gdb_test "mem 0x50 0x70 ro" "overlapping memory region" "mem 0x50 0x70 1"
+gdb_test "mem 0x20 0x0 ro" "overlapping memory region" "mem 0x20 0x0 1"
+gdb_test "mem 0x30 0x0 ro" "overlapping memory region" "mem 0x30 0x0 1"
+gdb_test_no_output "mem 0x10 0x30 ro" "mem 0x10 0x30 1"
+gdb_test_no_output "mem 0x60 0x80 ro" "mem 0x60 0x80 1"
+gdb_test_no_output "mem 0x80 0x0 ro" "mem 0x80 0x0 1"
+
+# Test special case (upper == 0)
+delete_memory
+gdb_test_no_output "mem 0x30 0x0 ro"
+gdb_test "mem 0x20 0x40 ro" "overlapping memory region" "mem 0x20 0x40 2"
+gdb_test "mem 0x30 0x40 ro" "overlapping memory region" "mem 0x30 0x40 2"
+gdb_test "mem 0x20 0x0 ro" "overlapping memory region" "mem 0x20 0x0 2"
+gdb_test "mem 0x30 0x0 ro" "overlapping memory region" "mem 0x30 0x0 2"
+gdb_test_no_output "mem 0x10 0x30 ro" "mem 0x10 0x30 2"


  reply	other threads:[~2012-08-16 10:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-02  6:11 Wei-cheng Wang
2012-08-02  8:10 ` Yao Qi
2012-08-02 10:00   ` Wei-cheng Wang
2012-08-03 10:54 ` Yao Qi
2012-08-07  2:35   ` Wei-cheng Wang
2012-08-07  2:48     ` Yao Qi
2012-08-07  6:02       ` Wei-cheng Wang
2012-08-08 10:31         ` Yao Qi
2012-08-16 10:03           ` Wei-cheng Wang [this message]
2012-08-24 11:18             ` Pedro Alves
2012-08-24 11:47               ` Wei-cheng Wang
2012-08-24 15:12                 ` Pedro Alves
2012-08-27  2:22                   ` Wei-cheng Wang
2012-08-27  8:58                     ` Pedro Alves

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='CAPmZyH4tJS=DyhL+3eJFkG=1yD5ttXS5t7=ffzgK6PGKcxmBrA@mail.gmail.com' \
    --to=cole945@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=yao@codesourcery.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