From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 546 invoked by alias); 16 Jan 2014 09:51:31 -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 537 invoked by uid 89); 16 Jan 2014 09:51:30 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 16 Jan 2014 09:51:30 +0000 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id s0G9pRLT010835 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 16 Jan 2014 04:51:27 -0500 Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.ams2.redhat.com [10.39.146.11]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id s0G9pP9V006010; Thu, 16 Jan 2014 04:51:26 -0500 Message-ID: <52D7AB9D.8020108@redhat.com> Date: Thu, 16 Jan 2014 09:51:00 -0000 From: Pedro Alves User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130625 Thunderbird/17.0.7 MIME-Version: 1.0 To: Pedro Alves CC: Omair Javaid , Yao Qi , gdb-patches@sourceware.org Subject: Re: [PATCH] testsuite/gdb.dwarf2: Fix for dw2-ifort-parameter failure on ARM References: <51E4B587.70007@codesourcery.com> <5280A528.8040308@codesourcery.com> <52D7A05F.6070304@linaro.org> <52D7AAF1.80501@redhat.com> In-Reply-To: <52D7AAF1.80501@redhat.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2014-01/txt/msg00591.txt.bz2 On 01/16/2014 09:48 AM, Pedro Alves wrote: > On 01/16/2014 09:03 AM, Omair Javaid wrote: > >> There seemed no problem with how breakpoint addresses were being adjusted. >> This test requires to build dwarf info by hand in dw2-ifort-parameter-debug.S >> using compile time addresses so in case of arm (thumb mode) the least >> significant bits of compile time address are set to 1. For that reason >> 0x000083bd was being used as a breakpoint address func. > > OOC, what does the compiler debug info usually do instead to avoid this? Also: > warning: Breakpoint address adjusted from 0x000083bd to 0x000083bc. > Breakpoint 1 at 0x83bc (2 locations) why 2 locations? -- Pedro Alves