Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Ingham <jingham@apple.com>
To: Bob Rossi <bob@brasko.net>
Cc: Alain Magloire <alain@qnx.com>, Eli Zaretskii <eliz@gnu.org>,
	Andrew Cagney <cagney@gnu.org>,
	nick@nick.uklinux.net, gdb-patches@sources.redhat.com
Subject: Re: MI handshaking
Date: Wed, 05 Jan 2005 01:51:00 -0000	[thread overview]
Message-ID: <AFDD082F-6704-4739-A49F-C41A86D2050A@apple.com> (raw)
In-Reply-To: <20050105013617.GB25675@white>


On Jan 4, 2005, at 5:36 PM, Bob Rossi wrote:

>>
>> I've been very busy, so sorry about the delay.
>>
>> I'll look into what we discussed here and come up with something that
>> fits all the new needs. Does Jim care about any of this?

I didn't see this question in the original note.  The answer is we 
always ship the Developer Tools as a whole package, which includes 
Xcode & gdb, and just ask for the mi version we know it supports 
explicitly.  We don't support taking one version of gdb & using it 
under an older or newer version of Xcode.  I don't see any plans for us 
to separate the two in the forseeable future.  So while I do care about 
this in an abstract sort of way, I can't see us using it.


>
> Sorry about the delay.
>
> I plan on getting at least this patch into GDB. So, to recap, I neede 
> to add
> a new mi-command that would output all of the info discovered during 
> the
> handshaking phase. Is there anything else that needs to be added?
>

Xcode does use the "does this command exist" mi command Jason mentioned 
in a few places.  This was more for the convenience of the Xcode 
developers - so they could ask me to implement a command, then sketch 
out the implementation right away without having to wait for me to 
implement it.  That is the level of handshaking that we do.

Jim


  reply	other threads:[~2005-01-05  1:51 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200411120344.WAA24018@smtp.ott.qnx.com>
2004-11-12 22:59 ` Andrew Cagney
2004-11-13  9:01   ` Eli Zaretskii
2004-11-13 13:48     ` Bob Rossi
2004-11-17 16:05       ` Alain Magloire
2004-11-17 16:32         ` Bob Rossi
2004-11-18  1:35           ` Alain Magloire
     [not found]           ` <200411180135.UAA14730@smtp.ott.qnx.com>
2004-11-19 19:23             ` Bob Rossi
2005-01-05  1:36               ` Bob Rossi
2005-01-05  1:51                 ` Jim Ingham [this message]
2005-01-05  1:53                   ` Bob Rossi
2005-01-05  2:01                     ` Jim Ingham
2005-01-05  2:34                       ` Bob Rossi
2005-01-05  2:40                         ` Bob Rossi
2004-11-17 16:05     ` Alain Magloire
     [not found] <200411171514.KAA17361@smtp.ott.qnx.com>
2004-11-17 17:30 ` Eli Zaretskii
2004-11-12  9:54 Nick Roberts
  -- strict thread matches above, loose matches on Subject: below --
2004-11-04 19:57 Bob Rossi
2004-11-04 19:59 ` Bob Rossi
2004-11-11 20:30   ` Andrew Cagney
2004-11-12  3:44     ` Alain Magloire
2004-11-04 21:28 ` Eli Zaretskii
2004-11-05 16:39   ` Bob Rossi
2004-11-05 17:50     ` Eli Zaretskii
2004-11-05 22:12       ` Bob Rossi
2004-11-06 10:12         ` Eli Zaretskii
2004-11-08 14:49           ` Bob Rossi
2004-11-08 15:01             ` Eli Zaretskii

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=AFDD082F-6704-4739-A49F-C41A86D2050A@apple.com \
    --to=jingham@apple.com \
    --cc=alain@qnx.com \
    --cc=bob@brasko.net \
    --cc=cagney@gnu.org \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=nick@nick.uklinux.net \
    /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