Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Thomas Schwinge <thomas@codesourcery.com>
To: Pedro Alves <palves@redhat.com>, Yue Lu <hacklu.newborn@gmail.com>
Cc: gdb-patches <gdb-patches@sourceware.org>,
	Luis Machado	<lgustavo@codesourcery.com>, <bug-hurd@gnu.org>
Subject: Re: [PATCH 1/2] Port gdbserver to GNU/Hurd
Date: Tue, 03 Sep 2013 13:09:00 -0000	[thread overview]
Message-ID: <877geyhx1j.fsf@kepler.schwinge.homeip.net> (raw)
In-Reply-To: <5225C3C6.8090101@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1096 bytes --]

Hi!

On Tue, 03 Sep 2013 12:11:02 +0100, Pedro Alves <palves@redhat.com> wrote:
> On 09/03/2013 10:38 AM, Thomas Schwinge wrote:
> > [strategy]
> 
> I've been thinking about this this morning, after seeing these
> patches.
> 
> For new gdbserver ports, this path just seems to swim further away from
> a full sharing approach, by adding lots duplication as first step, [...]

> So my idea would be, [...]

Understood, and yes, your argumentation is reasonable.

> I'd do this [by]
> literally moving gdbserver/gnu-low.c on top of gdb/gnu-nat.c (etc.), and
> use git diff to guide me through, in identifying what would need to
> be restored, and guarded with #if[n]def GDBSERVER.  [...]

Yes, that's a nice technique for displaying and integrating the
differences between the existing Hurd native port's files and the new
gdbserver port's.  Yue, does the approach of diffing the files as Pedro
described make sense to you?  Please tell if you need help with how to
use Git to do that, etc.

> Could we try that approach?

Thanks for the input!


Grüße,
 Thomas

[-- Attachment #2: Type: application/pgp-signature, Size: 489 bytes --]

  reply	other threads:[~2013-09-03 13:09 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAB8fV=jJ64i91VW52ZmdnEDZhd1ZGTAykDqoFyPJanCP=5beqA@mail.gmail.com>
2013-09-03  8:03 ` [PATCH 2/2] " Yue Lu
2013-09-03  9:38   ` [PATCH 1/2] " Thomas Schwinge
2013-09-03 11:11     ` Pedro Alves
2013-09-03 13:09       ` Thomas Schwinge [this message]
2013-09-04  1:47         ` Yue Lu
2013-09-04  1:38       ` Yue Lu
2013-09-05 10:54       ` Yue Lu
2013-09-05 19:29         ` Pedro Alves
2013-09-05 19:39           ` Joel Brobecker
2013-09-05 21:38           ` Thomas Schwinge
2013-09-08 13:35             ` Yue Lu
2013-09-09  9:58               ` Thomas Schwinge
2013-09-18 12:12                 ` Pedro Alves
2013-09-18 13:48                   ` Yue Lu
2013-09-18 14:52                     ` [Hurd/gnu-nat.c] Use ptid_t.lwpid to store, thread ids instead of ptid_t.tid. (was: Re: [PATCH 1/2] Port gdbserver to GNU/Hurd) Pedro Alves
2013-09-18 14:57                     ` [PATCH 1/2] Port gdbserver to GNU/Hurd Pedro Alves
2013-09-22 12:58             ` Yue Lu
2013-09-06 18:53           ` Pedro Alves
2013-09-12  3:05             ` Yue Lu
2013-09-18 12:30               ` Pedro Alves
2013-09-18 12:37               ` Pedro Alves
2013-09-19  7:41                 ` Yue Lu
2013-09-19  8:30                   ` FAIL: gdb.base/nextoverexit.exp: next over exit (the program exited) (was: [PATCH 1/2] Port gdbserver to GNU/Hurd) Thomas Schwinge
2013-09-19  8:44                     ` FAIL: gdb.base/nextoverexit.exp: next over exit (the program exited) Pedro Alves
2013-09-09 10:21           ` [PATCH 1/2] Port gdbserver to GNU/Hurd Yue Lu

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=877geyhx1j.fsf@kepler.schwinge.homeip.net \
    --to=thomas@codesourcery.com \
    --cc=bug-hurd@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=hacklu.newborn@gmail.com \
    --cc=lgustavo@codesourcery.com \
    --cc=palves@redhat.com \
    /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