From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-prs-return-17515-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Received: (qmail 9072 invoked by alias); 20 Feb 2015 12:41:48 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Received: (qmail 15670 invoked by uid 48); 20 Feb 2015 12:27:19 -0000
From: "qiyao at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/18003] New: Some fails in
 gdb.base/breakpoint-in-ro-region.exp
Date: Fri, 20 Feb 2015 12:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: gdb
X-Bugzilla-Version: HEAD
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: qiyao at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status
 bug_severity priority component assigned_to reporter
Message-ID: <bug-18003-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-q1/txt/msg00280.txt.bz2

https://sourceware.org/bugzilla/show_bug.cgi?id=18003

            Bug ID: 18003
           Summary: Some fails in gdb.base/breakpoint-in-ro-region.exp
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: qiyao at gcc dot gnu.org

I see some fails as below on aarch64-linux-gnu target, in both remote and
native testing...

si^M
0x0000000000400738      23        i = 0;^M
(gdb) FAIL: gdb.base/breakpoint-in-ro-region.exp: always-inserted off: auto-hw
off: step in ro region

si^M
0x0000000000400740      24        i = 0;^M
(gdb) FAIL: gdb.base/breakpoint-in-ro-region.exp: always-inserted on: auto-hw
off: step in ro region

looks the hex is unexpected to the pattern matching,

    set test "step in ro region"
    gdb_test_multiple "si" $test {
    -re "Could not insert hardware breakpoints.*$gdb_prompt $" {
        gdb_assert {!$hw_step && $auto_hw == "on" && !$supports_hbreak} \
        "$test (cannot insert hw break)"
    }
    -re "Cannot set software breakpoint at read-only address
$next_insn.*$gdb_prompt $" {
        gdb_assert {!$hw_step && $auto_hw == "off"} \
        "$test (cannot insert sw break)"
    }
    -re "^si\r\nNote: automatically using hardware breakpoints for read-only
addresses\.\r\n${decimal}\[ \t\]+i = 0;\r\n$gdb_prompt $" {
        gdb_assert {!$hw_step && $auto_hw == "on" && $supports_hbreak} \
        "$test (auto-hw)"
    }
    -re "^si\r\n${decimal}\[ \t\]+i = 0;\r\n$gdb_prompt $" {
        gdb_assert {$hw_step || ($auto_hw == "on" && $supports_hbreak)} \
        "$test (no error)"
    }
    }

further analysis is needed.

-- 
You are receiving this mail because:
You are on the CC list for the bug.