From: Andrew Cagney <ac131313@cygnus.com>
To: brendan@dgs.monash.edu.au
Cc: gdb@sourceware.cygnus.com, insight@sourceware.cygnus.com
Subject: Re: GDB and Insight CVS repositories.
Date: Wed, 18 Aug 1999 18:45:00 -0000 [thread overview]
Message-ID: <37BB6197.627A5E05@cygnus.com> (raw)
In-Reply-To: <37BB5E59.C4BB46BC@dgs.monash.edu.au>
Brendan Simon wrote:
> From a purist point of view I think it would be better to keep the packages
> seperate, regardless of whether Insight is built as a seperate application or
> an integrated application. If it is relatively simple to unpack Insight
> sources into a seperate sub directory of the GDB source then this sounds like
> it would keep RMS happy and keep the GUI repository seperate from the GDB
> repository. I guess this is akin to gcc-core, gcc-c++, gcc-fortran, etc
> distribution archives. I guess the difference is that all these components
> are officialy accepted by GNU.
>
> If this was to happen, would this mean that gdb would require patches ?
At present yes. However, I believe that that can be fixed.
See separate my separate e-mail about --with-gdb-interpreter=... No one
has sat down and taken the time to revamp the startup code so that a
second interpreter can be dropped on - not hard, just needs to be done.
>
> Does GDB have an external API (interprocess comms, TCP/UDP sockets) so that
> other GUIs could communicate without having to parse CLI output ?
Hmm, your doing well. My things to do today includes write up an
additional e-mail putting forward a way that GDB can progress on this
issue.
Andrew
prev parent reply other threads:[~1999-08-18 18:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-18 16:56 Brendan Simon
1999-08-18 17:26 ` Andrew Cagney
1999-08-18 17:42 ` Stan Shebs
1999-08-18 18:30 ` Brendan Simon
1999-08-18 18:45 ` Andrew Cagney [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=37BB6197.627A5E05@cygnus.com \
--to=ac131313@cygnus.com \
--cc=brendan@dgs.monash.edu.au \
--cc=gdb@sourceware.cygnus.com \
--cc=insight@sourceware.cygnus.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).