From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 55896 invoked by alias); 23 Feb 2017 14:47:42 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 55851 invoked by uid 89); 23 Feb 2017 14:47:41 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=H*MI:sk:093bd3d, H*i:sk:093bd3d, H*f:sk:093bd3d, earth X-HELO: relay1.mentorg.com Received: from relay1.mentorg.com (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 23 Feb 2017 14:47:39 +0000 Received: from svr-orw-mbx-03.mgc.mentorg.com ([147.34.90.203]) by relay1.mentorg.com with esmtp id 1cgugE-0005bo-Dm from Luis_Gustavo@mentor.com ; Thu, 23 Feb 2017 06:47:38 -0800 Received: from [172.30.12.171] (147.34.91.1) by svr-orw-mbx-03.mgc.mentorg.com (147.34.90.203) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 23 Feb 2017 06:47:33 -0800 Reply-To: Luis Machado Subject: Re: [PATCH] Restrict gdb.base/gcore-relro-pie.exp to native/linux targets References: <1487859197-6269-1-git-send-email-lgustavo@codesourcery.com> <093bd3d5-9723-2412-a736-8f29686d4a8a@redhat.com> To: Pedro Alves , From: Luis Machado Message-ID: <6e1f21a5-3283-b30e-d7fa-e2c1453af882@codesourcery.com> Date: Thu, 23 Feb 2017 14:47:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0 MIME-Version: 1.0 In-Reply-To: <093bd3d5-9723-2412-a736-8f29686d4a8a@redhat.com> Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit X-ClientProxiedBy: svr-orw-mbx-03.mgc.mentorg.com (147.34.90.203) To svr-orw-mbx-03.mgc.mentorg.com (147.34.90.203) X-IsSubscribed: yes X-SW-Source: 2017-02/txt/msg00621.txt.bz2 On 02/23/2017 08:24 AM, Pedro Alves wrote: > On 02/23/2017 02:13 PM, Luis Machado wrote: >> This particular test doesn't work correctly on aarch64-elf for a couple >> reasons. >> >> First, the test is supposed to crash and bare-metal targets are not always >> ready to handle such exceptions like Linux does. In our case the board just >> keeps cycling within an ISR function. > > Hmm? AFAICS, the testcase is generating the core with gdb_gcore_cmd. > How on earth is that causing this cycling? I tend to see this particular target stopping later in the source file compared to x86. I had an (incorrect) assumption it was dereferencing NULL when running to break_here, but it doesn't seem to be the case. It stops right at what would cause the crash: (gdb) b break_here Breakpoint 2 at 0x80000a20 (gdb) disass break_here Dump of assembler code for function break_here: 0x0000000080000a1c <+0>: mov x0, #0x0 0x0000000080000a20 <+4>: str wzr, [x0] It seems something is off with startup code/stack pointer then. Back to the drawing board. I still think it doesn't make much sense to run these tests if we're not sure gcore will support them. They may run a few early tests/setup tests, but that won't translate into meaningful PASSes. But i'm ok keeping it as-is if others think the early test PASSes are useful.