From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26547 invoked by alias); 5 May 2013 17:35:28 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 26534 invoked by uid 89); 5 May 2013 17:35:28 -0000 X-Spam-SWARE-Status: No, score=-4.5 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.1 Received: from mail-ve0-f180.google.com (HELO mail-ve0-f180.google.com) (209.85.128.180) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Sun, 05 May 2013 17:35:27 +0000 Received: by mail-ve0-f180.google.com with SMTP id pa12so2694716veb.11 for ; Sun, 05 May 2013 10:35:25 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:x-gm-message-state; bh=eAujJgGu/QaArgaEw+i+XYBjjZiWL5fTQ/ne/ZvediI=; b=mCgxXZ2Tz34OB1ttp6kuSW1okzXn/z7UGmUlE5TQ5P2gggDJ5OZbP3WmBt59nP9jsU El/Jli4d13yTySGkcvj310bgs6IAoTfe6AwSmnpAC5RKPSq0go1azILUzv5cbpsGdHNK oLooHkJuvmMh0cKa5QVf9khoHn7cGkACe+tg9Dy5hRed9ZR/Mjkr37e716wzwqv1QRt0 epX1SZaeHEPup4FhHDSu/b3r04TXoKJQA6J+gGlu06dAuozSQVXMhjEsKujJGo+5QhE6 Mvi+4ISwQ/m3g4jyAOYuZGDp0I6+PxMCo2MPqPQh2PEHNyXlHWjwqKOaEbO8kAeymYOV aFNg== MIME-Version: 1.0 X-Received: by 10.52.174.208 with SMTP id bu16mr71614vdc.21.1367775325726; Sun, 05 May 2013 10:35:25 -0700 (PDT) Received: by 10.220.173.7 with HTTP; Sun, 5 May 2013 10:35:25 -0700 (PDT) In-Reply-To: References: <8738u4sc19.fsf@kepler.schwinge.homeip.net> Date: Sun, 05 May 2013 17:35:00 -0000 Message-ID: Subject: Re: [patch] for mig check in GDB's configure From: Doug Evans To: Yue Lu Cc: Thomas Schwinge , bug-hurd@gnu.org, gdb-patches Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQni4OaBVCTh6/zkq/tOVHBhhoE7YnkM09wUI/ie8rnwVUlhWS78ffUohtyJLp523WjDlknxeoxlc8VijPE/SoIvHpx4myB7SqTkSVcZgdEwbkf9TLpbLPwxPNg3H1AB3ag6hBfrPG0kXmemucLYG3pb2g76Cn1ywaSpbNoN25rQPR91WNxMBFtJqKKLFm1UtvVZKDABP48eGBKf7A3H/cp1Oopx5w== X-SW-Source: 2013-05/txt/msg00085.txt.bz2 On Sat, May 4, 2013 at 10:30 PM, Yue Lu 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.