From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3888 invoked by alias); 15 Jun 2015 10:02:14 -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 3876 invoked by uid 89); 15 Jun 2015 10:02:13 -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,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-pd0-f169.google.com Received: from mail-pd0-f169.google.com (HELO mail-pd0-f169.google.com) (209.85.192.169) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Mon, 15 Jun 2015 10:02:12 +0000 Received: by pdjn11 with SMTP id n11so69675734pdj.0 for ; Mon, 15 Jun 2015 03:02:11 -0700 (PDT) X-Received: by 10.70.130.35 with SMTP id ob3mr25469488pdb.64.1434362531230; Mon, 15 Jun 2015 03:02:11 -0700 (PDT) Received: from E107787-LIN (gcc1-power7.osuosl.org. [140.211.15.137]) by mx.google.com with ESMTPSA id pr4sm11676478pbb.30.2015.06.15.03.02.09 (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Mon, 15 Jun 2015 03:02:10 -0700 (PDT) From: Yao Qi To: Joel Brobecker Cc: Martin Simmons , gdb-patches@sourceware.org Subject: Re: [PATCH] Prevent internal-error when computing $pc in ARM assembly code References: <201505200949.t4K9nlqt015737@heapu.cam.lispworks.com> <20150609184408.GG2855@adacore.com> Date: Mon, 15 Jun 2015 10:02:00 -0000 In-Reply-To: <20150609184408.GG2855@adacore.com> (Joel Brobecker's message of "Tue, 9 Jun 2015 14:44:08 -0400") Message-ID: <86wpz5s31d.fsf@gmail.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes X-SW-Source: 2015-06/txt/msg00294.txt.bz2 Joel Brobecker writes: > It would be good to have a few more details about what causes us > to be in a situation where we'd be failing to read memory at > an address. Perhaps just showing the disassembled code and > a quick explanation of what happens might be sufficient. I agree with Joel that we need more details about the problem you are trying to fix. --=20 Yao (=E9=BD=90=E5=B0=A7)