Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: drow@mvista.com
Cc: ac131313@cygnus.com, gdb-patches@sources.redhat.com, dj@delorie.com
Subject: Re: [RFA] Type cleanups
Date: Sat, 18 May 2002 00:13:00 -0000	[thread overview]
Message-ID: <6436-Sat18May2002101204+0300-eliz@is.elta.co.il> (raw)
In-Reply-To: <20020517172146.GA13021@nevyn.them.org> (message from Daniel Jacobowitz on Fri, 17 May 2002 13:21:46 -0400)

> 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.


      parent reply	other threads:[~2002-05-18  7:13 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-12 17:34 Daniel Jacobowitz
2002-05-12 20:18 ` Andrew Cagney
2002-05-12 20:40   ` Daniel Jacobowitz
2002-05-12 21:31     ` Andrew Cagney
2002-05-13 11:46       ` Daniel Jacobowitz
2002-05-13 12:54         ` Daniel Berlin
2002-05-13 12:57           ` Daniel Jacobowitz
2002-05-13  6:59   ` Daniel Jacobowitz
2002-05-13  8:37     ` Andrew Cagney
2002-05-13  8:51       ` Elena Zannoni
2002-05-13  9:11         ` Andrew Cagney
2002-05-13  9:19           ` Elena Zannoni
2002-05-13 11:50       ` Daniel Jacobowitz
2002-05-13 11:59         ` Daniel Jacobowitz
2002-05-13 15:14           ` Andrew Cagney
2002-05-13 16:09             ` Daniel Jacobowitz
2002-05-13 18:37               ` Elena Zannoni
2002-05-14 17:09               ` Andrew Cagney
2002-05-17  1:11     ` Eli Zaretskii
2002-05-17  8:02       ` Daniel Jacobowitz
2002-05-17  9:14         ` Eli Zaretskii
2002-05-17 10:21           ` Daniel Jacobowitz
2002-05-17 10:34             ` Andrew Cagney
2002-05-18  0:15               ` Eli Zaretskii
2002-05-18  0:13             ` Eli Zaretskii [this message]

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=6436-Sat18May2002101204+0300-eliz@is.elta.co.il \
    --to=eliz@is.elta.co.il \
    --cc=ac131313@cygnus.com \
    --cc=dj@delorie.com \
    --cc=drow@mvista.com \
    --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