This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [patch] for mig check in GDB's configure
- From: Doug Evans <dje at google dot com>
- To: Yue Lu <hacklu dot newborn at gmail dot com>
- Cc: Thomas Schwinge <thomas at codesourcery dot com>, bug-hurd at gnu dot org, gdb-patches <gdb-patches at sourceware dot org>
- Date: Sun, 5 May 2013 10:35:25 -0700
- Subject: Re: [patch] for mig check in GDB's configure
- References: <CAB8fV=gfGtguD28FGa-A5DZT8jqvEA1AoaK4dO=cHMQcCVvB-w at mail dot gmail dot com> <8738u4sc19 dot fsf at kepler dot schwinge dot homeip dot net> <CAB8fV=hrvCmRd1AkMwvFsYZq1tC=7AgExWEfHLAURu6iWo3pTQ at mail dot gmail dot com> <CADPb22TG+2HbbwcWu5-XQvmpkDu5SAXVP7q7CC-EafM+Df0SSg at mail dot gmail dot com> <CAB8fV=joJMkdPBjOH1QDaaJkCJZFyi1uTxf-OYjBWmRge321Cg at mail dot gmail dot 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.