From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19312 invoked by alias); 13 Feb 2019 00:32:29 -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 19302 invoked by uid 89); 13 Feb 2019 00:32:28 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=dbx, manifest, mean-time, dive X-HELO: mail-it1-f176.google.com Received: from mail-it1-f176.google.com (HELO mail-it1-f176.google.com) (209.85.166.176) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 13 Feb 2019 00:32:27 +0000 Received: by mail-it1-f176.google.com with SMTP id v72so1599348itc.0 for ; Tue, 12 Feb 2019 16:32:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=s7X1seFq7cD5SNaCVC5EUi3jUnKDuy3IwqnQtFVtzqg=; b=CwI0gzZe1nvEouBxcNQxD4NskarWfdq24ZCJLMNDV1tCLeTMm0kEjFFkEFo9HdZZ5/ cN33kvq7ZKfTvMLHWFVkkzC607hW1OuNr4/gmZGI/NV+gARmz9TV2HqgAa5bx1JZ1j8/ dBt6NjPfjLloN0/rJkeb0y0l4PLqD4XONxp89ZjJfZ6h7lusXWuf3GDkorQqqlbOhZIL KruV9wCItqdwKgca8UZKjurob2uDl3YPlya64JlILtVMN5XabHJCVJtO9o4ktZNg+ptv PxDCpskMeXQTIL2l3t+RDnQmfNybyAdQTTaErXEBNsdmiJKewege4rI3F4lYB6KQAnCZ W8ww== MIME-Version: 1.0 References: <657f3267-c77a-096f-561b-96136c5efc4f@redhat.com> <20190209041209.GO6371@adacore.com> <20190212030925.GE17730@adacore.com> In-Reply-To: <20190212030925.GE17730@adacore.com> From: Brian Vandenberg Date: Wed, 13 Feb 2019 00:32:00 -0000 Message-ID: Subject: Re: gdbserver sparc solaris To: Joel Brobecker Cc: Pedro Alves , gdb@sourceware.org Content-Type: text/plain; charset="UTF-8" X-SW-Source: 2019-02/txt/msg00015.txt.bz2 > > > GDB is crashing when trying to debug directly on the machine and I > haven't > > had the time to dive in to figure out why; we've had to limp along using > > dbx from Solaris Studio in the mean-time. I had hoped if I could get > > remote debugging to work perhaps the problem wouldn't manifest or would > > help shed light on the problem by causing a different problem. > > Have you tried other, maybe older versions of GDB, to see if they fare > better? > Sometime during 6.x or early to mid 7.x gdb became broken on sparc solaris, so the earliest I've tried is ~7.8 (with variants of the patches I submitted over the last few months that address them). I'm fairly sure if I go back far enough that it's [semi?-]functional it would be too old because we're making use of C++11/14-isms. -brian