From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3789 invoked by alias); 16 Oct 2018 18:21:20 -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 3779 invoked by uid 89); 16 Oct 2018 18:21:20 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-0.9 required=5.0 tests=BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE autolearn=no version=3.3.2 spammy=Hx-languages-length:1076, oracle, sadly, Sound X-HELO: atl4mhob07.registeredsite.com Received: from atl4mhob07.registeredsite.com (HELO atl4mhob07.registeredsite.com) (209.17.115.45) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 16 Oct 2018 18:21:19 +0000 Received: from mailpod.hostingplatform.com (atl4qobmail01pod2.registeredsite.com [10.30.77.35]) by atl4mhob07.registeredsite.com (8.14.4/8.14.4) with ESMTP id w9GILEMQ013938 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for ; Tue, 16 Oct 2018 14:21:15 -0400 Received: (qmail 45090 invoked by uid 0); 16 Oct 2018 18:21:14 -0000 X-TCPREMOTEIP: 174.118.245.214 X-Authenticated-UID: dclarke@blastwave.org Received: from unknown (HELO ?172.16.35.3?) (dclarke@blastwave.org@174.118.245.214) by 0 with ESMTPA; 16 Oct 2018 18:21:14 -0000 Subject: Re: Obsoleting Solaris 10 support To: gdb@sourceware.org References: <20181016142024.GD17534@adacore.com> <20181016163907.GF17534@adacore.com> From: Dennis Clarke Message-ID: <10821a81-f740-ca9f-2606-b6ae88988eee@blastwave.org> Date: Tue, 16 Oct 2018 18:21: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: <20181016163907.GF17534@adacore.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2018-10/txt/msg00031.txt.bz2 On 10/16/2018 12:39 PM, Joel Brobecker wrote: >> this would argue for an obsoletion in the GDB 8.4 timeframe, roughly at >> the same time GCC itself does. Issues I'm facing with Solaris 10 right >> now (apart from the S10-only build breakages) are having to deal with >> different syscall numbers while working on an xml syscall table for >> Solaris and catch syscall support, as well as differences in corefile >> contents. I suspect there will be more as time goes on. > > Sound good. Feel free to step in and make suggestions if you have > new info that makes you think we should stop support earlier. > I can not think of a valid compelling reason to make the effort. I have had no major problems getting gcc bootstrapped on ye old s10 but I use dbx from the Sun/Oracle Studio line for debug work. If at all. Given that Oracle has dropped Solaris 10 into a legacy support status there isn't any valid reason for extra efforts to get gdb working flawlessly. At least I can not think of any. Sadly. Dennis Clarke ye old UNIX greybeard