From: Pedro Alves <palves@redhat.com>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Cc: Andreas Schwab <schwab@suse.de>, gdb-patches@sourceware.org
Subject: Re: Obsolete/remove Solaris < 10 [was: Re: Fix gdb 8.1 Solaris compilation]
Date: Fri, 22 Sep 2017 15:40:00 -0000 [thread overview]
Message-ID: <bf5aca6c-998d-4854-9e58-8677338ea630@redhat.com> (raw)
In-Reply-To: <ydd7ewqpzc9.fsf@CeBiTec.Uni-Bielefeld.DE>
On 09/22/2017 03:44 PM, Rainer Orth wrote:
>> On 09/21/2017 03:30 PM, Rainer Orth wrote:
>
>> all these years stepped forward, I think we should be able to just drop
>> it. I think you've proposed this in the past, even. I very
>
> Indeed: I found a line or two of notes about it. Must have been in the
> context of removing support for unstructured /proc in procfs.c and
> friends. I've dusted off and completed that patch as well...
Yay, looking forward to that. :-)
>> much doubt anyone would step forward this time.
>
> Indeed. I've opened a tracking PR gdb/22185 and produced a first patch.
> It will need a bit more testing (especially on Linux which also uses
> proc-service.c), but it's basically straightforward.
Eh, the Solaris port doesn't actually use proc-service.c. The
Solaris proc-service implementation is directly in sol-thread.c.
I think proc-service.c was originally based on sol-thread.c, maybe
aiming at sharing at some point, and that's where it got the
PROC_SERVICE_IS_OLD handling from.
The patch looks good to me.
I mildly wonder if the adding of sol-thread.o could move
from gdb/configure.ac to gdb/configure.nat.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2017-09-22 15:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-21 13:02 Fix gdb 8.1 Solaris compilation Rainer Orth
2017-09-21 13:17 ` Andreas Schwab
2017-09-21 14:14 ` Rainer Orth
2017-09-21 14:31 ` Obsolete/remove Solaris < 10 [was: Re: Fix gdb 8.1 Solaris compilation] Rainer Orth
2017-09-21 14:39 ` Pedro Alves
2017-09-22 14:45 ` Rainer Orth
2017-09-22 15:40 ` Pedro Alves [this message]
2017-09-26 11:20 ` Rainer Orth
2017-09-26 11:26 ` Pedro Alves
2017-09-26 13:25 ` Rainer Orth
2017-09-26 13:45 ` Pedro Alves
2017-09-26 13:55 ` Rainer Orth
2017-09-26 14:18 ` Pedro Alves
2017-09-26 14:21 ` Pedro Alves
2017-10-03 13:01 ` Rainer Orth
2017-09-29 11:53 ` Eli Zaretskii
2017-09-21 14:21 ` Fix gdb 8.1 Solaris compilation Pedro Alves
2017-09-21 14:23 ` 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=bf5aca6c-998d-4854-9e58-8677338ea630@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
--cc=schwab@suse.de \
/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