From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 86198 invoked by alias); 8 Feb 2019 13:26:09 -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 85839 invoked by uid 89); 8 Feb 2019 13:26:08 -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 autolearn=ham version=3.3.2 spammy=H*i:sk:yddo97m, Etc, Common, H*f:sk:yddo97m X-HELO: mail-wr1-f51.google.com Received: from mail-wr1-f51.google.com (HELO mail-wr1-f51.google.com) (209.85.221.51) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 08 Feb 2019 13:26:05 +0000 Received: by mail-wr1-f51.google.com with SMTP id z3so3592618wrv.3 for ; Fri, 08 Feb 2019 05:26:05 -0800 (PST) Return-Path: Received: from ?IPv6:2001:8a0:f913:f700:4c97:6d52:2cea:997b? ([2001:8a0:f913:f700:4c97:6d52:2cea:997b]) by smtp.gmail.com with ESMTPSA id 2sm5149527wrg.89.2019.02.08.05.26.02 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 08 Feb 2019 05:26:02 -0800 (PST) Subject: Re: gdbserver sparc solaris To: Rainer Orth References: <657f3267-c77a-096f-561b-96136c5efc4f@redhat.com> Cc: Brian Vandenberg , gdb@sourceware.org From: Pedro Alves Message-ID: <22c2ef2a-061c-f2f8-da59-41f51afaa19c@redhat.com> Date: Fri, 08 Feb 2019 13:26:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2019-02/txt/msg00006.txt.bz2 On 02/08/2019 01:05 PM, Rainer Orth wrote: > Hi Pedro, Hi Rainer, >>> Is it possible to get gdbserver to work on sparc solaris? >> >> Not without someone porting gdbserver to solaris. > > I had a very quick look at that once, but the code is currently full of > Linux dependencies (...) Hmm, that doesn't seem correct? There should be no Linux dependencies like that. There are ports of GDBserver for Linux, Windows/mingw and NTO/QNX. Each of those gets its own *-low.c file, which is the equivalent of GDB's -nat.c files. So gdb/linux-nat.c is similar to gdbserver/linux-low.c. Etc. Basically, a Solaris port would mean copying over gdb/procfs.c and friends to gdbserver/, and adjusting them to gdbserver's interfaces. Well, ideally, we'd refactor the gdb/procfs.c code a bit so that we could use it for both gdb and gdbserver, instead of just copying over. The fact that the Linux backend implementations in gdb and gdbserver are different was a bad design mistake that we're still trying to correct [1] [2]. > (...) had no actual need for a port. Given that this > will be a major effort, I certainly won't undertake it myself. Certainly understandable! [1] https://sourceware.org/gdb/wiki/Common [2] https://sourceware.org/gdb/wiki/LocalRemoteFeatureParity Thanks, Pedro Alves