From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 72328 invoked by alias); 29 Nov 2018 02:23:04 -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 72053 invoked by uid 89); 29 Nov 2018 02:23:02 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy= X-HELO: mail-vs1-f65.google.com Received: from mail-vs1-f65.google.com (HELO mail-vs1-f65.google.com) (209.85.217.65) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 29 Nov 2018 02:23:00 +0000 Received: by mail-vs1-f65.google.com with SMTP id t17so214879vsc.8 for ; Wed, 28 Nov 2018 18:23:00 -0800 (PST) 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 :cc; bh=qy3PTBVqeztmkDOHIrhwB0f9HtxbTwxUZv3uEHn+rGg=; b=bQmc6oXqCeJVE6Ku+ly3lDO8HutyRippYE/NULRo77BQeJYjIa90SJJgMZKovFJB6s LlBqHkRxCU4O/gS8kHHKBJRR1iqJOm7hsC3Mpx3h7gg48fsjKCPZIZ8t7vktGYYJpJdg 8iBFyWHNEYVNee66WE+wBGZddZSiQvAH+UUdWKqCv9dM93rYdxEyn9njy7b+sQ//0GXR YsJyma8SsWjAxTf1aSkct8d3uf2JAx+7W4zUJ4ECdliZuG33u10jq52W1ngLmosy1H5h yU+pq2y0UV3iSk20up/pvoVMS70Z78NW1O/Bpz1x9j3tSBHHJlppUYn8HK7AyvRuXqdw hLYg== MIME-Version: 1.0 References: <20181128224953.22441-1-andrew.burgess@embecosm.com> In-Reply-To: <20181128224953.22441-1-andrew.burgess@embecosm.com> From: Jim Wilson Date: Thu, 29 Nov 2018 02:23:00 -0000 Message-ID: Subject: Re: [RFC] gdb/riscv: Add read_description method for riscv_linux_nat_target To: Andrew Burgess Cc: gdb-patches@sourceware.org, Palmer Dabbelt , John Baldwin Content-Type: text/plain; charset="UTF-8" X-SW-Source: 2018-11/txt/msg00529.txt.bz2 On Wed, Nov 28, 2018 at 2:49 PM Andrew Burgess wrote: > Adds riscv_linux_nat_target::read_description method to find a > suitable target description for the native linux target we are running > on. I tested this on my HiFive Unleashed running a 4.15 kernel with patches for gcc, gdb, and glibc support. It looks good. It correctly detects the FP register support. I get 3 extra failures FAIL: gdb.base/solib-display.exp: NO: continue FAIL: gdb.base/solib-display.exp: IN: continue FAIL: gdb.base/solib-display.exp: SEP: continue which looks a little odd since there is no obvious connection to the target description support, but this is repeatable so something is going on here. Anyways, I'm OK with this for now, we can worry about debugging this problem later. Jim