public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <dan@codesourcery.com>
To: Martin Rosenau <martin@rosenau-ka.de>
Cc: asmwarrior <asmwarrior@gmail.com>, gdb@sourceware.org
Subject: Re: New features for GDB under Windows
Date: Mon, 19 Jul 2010 14:15:00 -0000	[thread overview]
Message-ID: <20100719141443.GA21554@caradoc.them.org> (raw)
In-Reply-To: <4C43EFB4.3030105@rosenau-ka.de>

On Mon, Jul 19, 2010 at 08:24:52AM +0200, Martin Rosenau wrote:
> However I thinks pipes will only work with Cygwin (Unix simulation on
> Windows), not with native Windows (required by Mingw etc.). I still
> could apply my patch to the current version of ser-pipe.c, if it is desired.

I use pipes with a mingw32 every day, and so do our customers.  So, I
know it works.  But if you know of a remaining problem, then we could
discuss your patch.

> >>> And the new feature:
> >>> - Remote debugging using special DLLs (this is faster than TCP/IP or
> >>> pipes and allows you to add new hardware targets - like JTAG adapters -
> >>> without re-compiling the entire GDB)
> > 
> > I don't know if this is a desired feature.  It runs into maintenance
> > and GPL compliance problems.
> > 
> The GPL compliance problems are an old problem running GPL programs
> under Windows. In some Internet forum I read the discussion if it is
> allowed to run GPL programs under Windows at all (it is (nearly)
> impossible to run any program under Windows without using Windows'
> closed-source DLLs!)
> Unfortunately there was no final conclusion about this problem.

That's a completely different problem.  There's language in the GPL to
describe exactly what is going on in that situation; it's called the
"system library exception", IIRC.

> What I do not understand is the term "maintenance problems". Do you think
> - about compatibility problems (a DLL for 7.x could not run under 8.x)

This is the primary issue.  If we allow plugins, we need to define,
validate, maintain, and preserve an interface for them.  We don't want
to do that.  At least, I don't.

I've never seen a GDB that used external DLLs for target access and
didn't violate our understanding of the GPL (and I've seen at least
two that I can recall).

-- 
Daniel Jacobowitz
CodeSourcery

      reply	other threads:[~2010-07-19 14:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-17 19:54 Martin Rosenau
2010-07-18  4:04 ` asmwarrior
2010-07-18 13:12   ` Daniel Jacobowitz
2010-07-19  6:25     ` Martin Rosenau
2010-07-19 14:15       ` Daniel Jacobowitz [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=20100719141443.GA21554@caradoc.them.org \
    --to=dan@codesourcery.com \
    --cc=asmwarrior@gmail.com \
    --cc=gdb@sourceware.org \
    --cc=martin@rosenau-ka.de \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).