Obsoleting Solaris 10 support

Rainer Orth ro@CeBiTec.Uni-Bielefeld.DE
Wed Oct 17 12:39:00 GMT 2018

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 Orth, Center for Biotechnology, Bielefeld University

More information about the Gdb mailing list