From: Pedro Alves <palves@redhat.com>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Cc: Brian Vandenberg <phantall@gmail.com>, gdb@sourceware.org
Subject: Re: gdbserver sparc solaris
Date: Fri, 08 Feb 2019 13:26:00 -0000 [thread overview]
Message-ID: <22c2ef2a-061c-f2f8-da59-41f51afaa19c@redhat.com> (raw)
In-Reply-To: <yddo97mfn13.fsf@CeBiTec.Uni-Bielefeld.DE>
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
next prev parent reply other threads:[~2019-02-08 13:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-08 1:41 Brian Vandenberg
2019-02-08 12:51 ` Pedro Alves
2019-02-08 13:05 ` Rainer Orth
2019-02-08 13:26 ` Pedro Alves [this message]
2019-02-08 21:20 ` Brian Vandenberg
2019-02-09 4:12 ` Joel Brobecker
2019-02-11 19:31 ` Brian Vandenberg
2019-02-12 3:09 ` Joel Brobecker
2019-02-13 0:32 ` Brian Vandenberg
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=22c2ef2a-061c-f2f8-da59-41f51afaa19c@redhat.com \
--to=palves@redhat.com \
--cc=gdb@sourceware.org \
--cc=phantall@gmail.com \
--cc=ro@CeBiTec.Uni-Bielefeld.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