public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Quality Quorum <qqi@world.std.com>
To: Peter Reilley <micrio@mv.com>
Cc: GDB Discussion <gdb@sources.redhat.com>
Subject: Re: Where is GDB going
Date: Sun, 25 Feb 2001 21:22:00 -0000	[thread overview]
Message-ID: <Pine.SGI.4.21.0102260017550.18201-100000@world.std.com> (raw)
In-Reply-To: <007c01c09f99$636f5ff0$05d145cc@ppro>

> 
> There really is no need for including interfaces to targets that do not
> have GPL'ed monitors in the gdb standard source tree.   They are of
> no use unless you have bought the hardware.   On the other hand if
> we eliminate all such interfaces they there may be only a few
> interfaces left, which would decrease the value of gdb for everyone.

Yep, if the cost of linking with GDB is a (at least partial) disclosure 
of intellectual property, nobody would do it. 

Actually, situation will be even worse once protocol "loophole" is 
closed. I highly doubt that it will be possible to talk GDB remote
protocol to a proprietary target at all.

> Pete

Thanks,

Aleksey



  parent reply	other threads:[~2001-02-25 21:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-25 18:11 Peter Reilley
2001-02-25 20:52 ` Steven Johnson
2001-02-25 21:22 ` Quality Quorum [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-02-26 20:34 Peter Reilley
2001-02-23 13:52 Andrew Cagney
2001-02-23 14:21 ` Quality Quorum
2001-02-25 15:48   ` Steven Johnson
2001-02-25 21:15     ` Quality Quorum
2001-02-25 23:41       ` Per Bothner
2001-02-26  9:39         ` Quality Quorum
2001-02-26 13:45           ` Per Bothner
2001-02-26 16:29             ` Quality Quorum
2001-02-26 13:53           ` Steven Johnson

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=Pine.SGI.4.21.0102260017550.18201-100000@world.std.com \
    --to=qqi@world.std.com \
    --cc=gdb@sources.redhat.com \
    --cc=micrio@mv.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).