From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21316 invoked by alias); 17 May 2002 17:34:46 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 21296 invoked from network); 17 May 2002 17:34:45 -0000 Received: from unknown (HELO localhost.redhat.com) (216.138.202.10) by sources.redhat.com with SMTP; 17 May 2002 17:34:45 -0000 Received: from cygnus.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 155DA3E98; Fri, 17 May 2002 13:34:54 -0400 (EDT) Message-ID: <3CE53F3D.4030005@cygnus.com> Date: Fri, 17 May 2002 10:34:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0rc1) Gecko/20020429 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daniel Jacobowitz Cc: Eli Zaretskii , gdb-patches@sources.redhat.com, dj@delorie.com Subject: Re: [RFA] Type cleanups References: <20020513003359.GA11672@nevyn.them.org> <3CDF3081.1020900@cygnus.com> <20020513135950.GB19484@nevyn.them.org> <6480-Fri17May2002110920+0300-eliz@is.elta.co.il> <20020517150244.GA8388@nevyn.them.org> <968-Fri17May2002191307+0300-eliz@is.elta.co.il> <20020517172146.GA13021@nevyn.them.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-05/txt/msg00725.txt.bz2 > > Those are both valid. > > >> My point is that DJGPP debugging is very special: there's no OS >> provision for system calls like ptrace etc., so the only way to debug >> a DJGPP inferior is to run it natively under a specially built program >> that is linked against the DJGPP debug support library. I'm curious >> how does your cross build achieve that, since I believe neither >> gdbserver nor any of the remote-* modules support DJGPP as of now. > > > I didn't say it would be useful. But consult MAINTAINERS; everything > listed in the "Targets" section on a --target= line is currently > "expected" to be buildable as a cross debugger, to sanity check > changes. That's all I was doing. Yes. It exposes header files, not covered by the more generic i386-elf target, to the compiler. Andrew