From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 80781 invoked by alias); 13 Apr 2019 18:18:24 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 80772 invoked by uid 89); 13 Apr 2019 18:18:23 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-0.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy= X-HELO: mail-ua1-f43.google.com Received: from mail-ua1-f43.google.com (HELO mail-ua1-f43.google.com) (209.85.222.43) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sat, 13 Apr 2019 18:18:22 +0000 Received: by mail-ua1-f43.google.com with SMTP id n16so4290111uae.10 for ; Sat, 13 Apr 2019 11:18:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sifive.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=q2VK1WO3aAWTiRTC7fLi10gKRERToln/4iJ3DmxG4kQ=; b=T7KssPnint2E+o6o3xoiB7nSWk6xzNtfWb+MlisPPxWDtDW3bACzHJmiHNh1e2dhtE tjx6qKI16qbyEtImv9XaUJM6cmlcXGIyQpBznDrQsB7BrWNXk/3+iZbMDxjZNXap+Pdv nVFEQOOh9I3/pm1S54szVZrzKobsoaUVLv2R3EBLB6BAGfGt/7Jku8RnJAZlsrJfEdKq i/zxSTs7I6HxoB6yjdqe9Ls5gKsCceM0R8X+SaanqdZWQXTFLponJN0jCnqLrRXkXZGr D1X0Qn3nzJ5aVj/JcoG/tGCSr7/nON6vgylLxXedB/KswBny0GMrZayJpYhJJG2AEgyQ EUVA== MIME-Version: 1.0 References: In-Reply-To: From: Jim Wilson Date: Sat, 13 Apr 2019 18:18:00 -0000 Message-ID: Subject: Re: RISC-V and fake function debug info in the testsuite To: gdb@sourceware.org Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2019-04/txt/msg00004.txt.bz2 On Fri, Apr 12, 2019 at 5:17 PM Jim Wilson wrote: > The question is what to do next. On second thought, I realized I can fix it by wrapping the target memory read in a try/catch. I'm just not used to fixing problems that way. That defers the error from when we set the breakpoint to when we try to run, at which point we get an error trying to write a breakpoint instruction to an invalid address, which seems to be the way that this works on other targets. I already tried that and it does fix the testsuite failures that I'm looking at. Jim