From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11053 invoked by alias); 17 May 2002 17:21:45 -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 11022 invoked from network); 17 May 2002 17:21:43 -0000 Received: from unknown (HELO nevyn.them.org) (128.2.145.6) by sources.redhat.com with SMTP; 17 May 2002 17:21:43 -0000 Received: from drow by nevyn.them.org with local (Exim 3.35 #1 (Debian)) id 178lQI-0003Pp-00; Fri, 17 May 2002 13:21:46 -0400 Date: Fri, 17 May 2002 10:21:00 -0000 From: Daniel Jacobowitz To: Eli Zaretskii Cc: ac131313@cygnus.com, gdb-patches@sources.redhat.com, dj@delorie.com Subject: Re: [RFA] Type cleanups Message-ID: <20020517172146.GA13021@nevyn.them.org> Mail-Followup-To: Eli Zaretskii , ac131313@cygnus.com, gdb-patches@sources.redhat.com, dj@delorie.com 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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <968-Fri17May2002191307+0300-eliz@is.elta.co.il> User-Agent: Mutt/1.5.1i X-SW-Source: 2002-05/txt/msg00723.txt.bz2 On Fri, May 17, 2002 at 07:13:07PM +0300, Eli Zaretskii wrote: > > Date: Fri, 17 May 2002 11:02:44 -0400 > > From: Daniel Jacobowitz > > > > Cross build, not foreign host build - i.e. an i386-linux -> djgpp cross > > debugger. > > Sorry, I still don't understand: does this mean a remote debugger with > some stub on the remote DOS/Windows machine? Or maybe the stub (or > gdbserver) running inside DOSEmu on the GNU/Linux box? 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. > Do I understand correctly that the build in question uses > i386/tm-go32.h, and that its definition of JB_PC was the culprit? Yes. -- Daniel Jacobowitz Carnegie Mellon University MontaVista Software Debian GNU/Linux Developer