Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Dennis Clarke <dclarke@blastwave.org>
Cc: gdb@sourceware.org
Subject: Re: Obsoleting Solaris 10 support
Date: Wed, 17 Oct 2018 12:39:00 -0000	[thread overview]
Message-ID: <yddva60g31r.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <10821a81-f740-ca9f-2606-b6ae88988eee@blastwave.org> (Dennis	Clarke's message of "Tue, 16 Oct 2018 14:21:13 -0400")

Hi Dennis,

> 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.

indeed: while gdb works reasonably well on Solaris, I had a couple of
cases (often related to corrupted stacks) where dbx dealt with the issue
way better (or even at all) compared to gdb which could be thrown off-track.

> 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.

I hope to get a few fixes into gdb for the 8.3 release that would
benefit both Solaris 10 and 11, but after that, I'm done with S10.

	Rainer

-- 
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University


  reply	other threads:[~2018-10-17 12:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-16  9:42 Rainer Orth
2018-10-16 14:20 ` Joel Brobecker
2018-10-16 14:31   ` Rainer Orth
2018-10-16 16:39     ` Joel Brobecker
2018-10-16 18:21       ` Dennis Clarke
2018-10-17 12:39         ` Rainer Orth [this message]
2018-10-17 12:34       ` Rainer Orth
2018-10-16 18:41 ` Dennis Clarke
2018-10-17 12:42   ` Rainer Orth

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=yddva60g31r.fsf@CeBiTec.Uni-Bielefeld.DE \
    --to=ro@cebitec.uni-bielefeld.de \
    --cc=dclarke@blastwave.org \
    --cc=gdb@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox