Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@ges.redhat.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa/i386] Consolidate i386 targets
Date: Sun, 04 Aug 2002 10:44:00 -0000	[thread overview]
Message-ID: <3D4D67F6.10605@ges.redhat.com> (raw)
In-Reply-To: <Pine.SUN.3.91.1020804082800.17436F-100000@is>

> On Sat, 3 Aug 2002, Andrew Cagney wrote:
> 
> 
>> This patch replaces a number of explicit i386 (-aout, -coff, -elf, -pe) 
>> targets with a generic ``i386-*'' pattern.
>> 
>> It then updates the MAINTAINERS file so that only one i386 target is 
>> listed or building: i386-elf.  This should cut down on the number of 
>> targets that need building.
> 
> 
> Why is this part a good idea?  DJGPP is still supported, right?

Yes, DJGPP is definitly still supported.  DJGPP is a native 
configuration though, and the above list applies to the cross debuggers.

>>        * MAINTAINERS: Drop i386-aout and i586-pc-msdosdjgpp from target
>>        list.
> 
> 
> Did I miss something?

I don't think so.  My understanding of the thread:
http://sources.redhat.com/ml/gdb-patches/2002-05/msg00774.html

> Date: Fri, 17 May 2002 13:21:46 -0400
>> From: Daniel Jacobowitz <drow@mvista.com>
> 
>> > 
>> > 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.
> 
> 
> Then I don't think you (or anyone else on this list) should be
> concerned with these problems: IMHO, a failure to build a
> dysfunctional version of GDB is not a failure at all.

is that trying to ensure that a cross DJGPP debugger always builds isn't 
useful.

enjoy,
Andrew




  reply	other threads:[~2002-08-04 17:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-03 13:36 Andrew Cagney
2002-08-03 22:31 ` Eli Zaretskii
2002-08-04 10:44   ` Andrew Cagney [this message]
2002-08-04 21:46     ` Eli Zaretskii
2002-08-05 10:04       ` Andrew Cagney

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=3D4D67F6.10605@ges.redhat.com \
    --to=ac131313@ges.redhat.com \
    --cc=eliz@is.elta.co.il \
    --cc=gdb-patches@sources.redhat.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