From: Doug Evans <dje@google.com>
To: Yue Lu <hacklu.newborn@gmail.com>
Cc: Thomas Schwinge <thomas@codesourcery.com>,
bug-hurd@gnu.org, gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [patch] for mig check in GDB's configure
Date: Sun, 05 May 2013 17:35:00 -0000 [thread overview]
Message-ID: <CADPb22R-sbXDiHUEuPyYQGvUQaBxvCe+S7z8gRMmTJH_9=-7Cg@mail.gmail.com> (raw)
In-Reply-To: <CAB8fV=joJMkdPBjOH1QDaaJkCJZFyi1uTxf-OYjBWmRge321Cg@mail.gmail.com>
On Sat, May 4, 2013 at 10:30 PM, Yue Lu <hacklu.newborn@gmail.com> wrote:
> But I have one more question, why the one run on GNU Hurd which
> targeting arm doesn't need to use MIG? As it run under GNU Hurd, it
> must use the message transport facility and need to use MIG to
> generate the interface file automatically or someone write it by
> hands.
That's a good question (assuming I understand it, it's a bit hard to
parse as written). I don't know MIG or GNU Hurd.
This stuff is pretty straightforward though, there's no magic.
The answer depends on what GDB uses MIG for.
If GDB on Hurd uses MIG like GDB on Linux uses ptrace,
then that would explain it (again, assuming I understand the question).
But someone who knows Hurd and MIG will need to step up
and provide a real answer.
next prev parent reply other threads:[~2013-05-05 17:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAB8fV=gfGtguD28FGa-A5DZT8jqvEA1AoaK4dO=cHMQcCVvB-w@mail.gmail.com>
2013-05-03 8:28 ` Thomas Schwinge
2013-05-03 10:44 ` 陆岳
[not found] ` <87txmkxlu6.fsf@violet.siamics.net>
2013-05-04 8:29 ` Yue Lu
2013-05-16 21:55 ` Thomas Schwinge
2013-05-17 5:30 ` Joel Brobecker
2013-05-17 6:34 ` Yue Lu
2013-05-17 7:00 ` Thomas Schwinge
2013-05-17 7:07 ` Joel Brobecker
2013-05-04 17:22 ` Doug Evans
2013-05-05 5:31 ` Yue Lu
2013-05-05 17:35 ` Doug Evans [this message]
2013-05-16 22:10 ` Thomas Schwinge
2013-05-03 14:51 ` Pedro Alves
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='CADPb22R-sbXDiHUEuPyYQGvUQaBxvCe+S7z8gRMmTJH_9=-7Cg@mail.gmail.com' \
--to=dje@google.com \
--cc=bug-hurd@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=hacklu.newborn@gmail.com \
--cc=thomas@codesourcery.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