public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Bob Rossi <bob@brasko.net>
To: Jim Ingham <jingham@apple.com>
Cc: gdb@sources.redhat.com
Subject: Re: MI rules
Date: Sat, 25 Sep 2004 20:12:00 -0000	[thread overview]
Message-ID: <20040925201242.GA4133@white> (raw)
In-Reply-To: <4E6C7AD8-0F25-11D9-AD7A-000D932CB92C@apple.com>

On Sat, Sep 25, 2004 at 12:01:28PM -0700, Jim Ingham wrote:
> I have no strong opposition to this, I just don't see the point.
> 

Jim, I appreciate the time you have spent thinking about this issue for
me. I value the input from someone who has been working with MI for
quite some time. I have several questions for you,

   1. How do you figure out what type of asynchronous MI output command
   you just received is? 

   2. How do you deal with your MI front end dealing with snapshots of
   GDB? For example, it has new asynchronous commands, but the MI version 
   hasn't been bumped yet.


Finally, I want to make an analogy and I would like for someone to tell
me where my thinking went wrong.

   GDB and a leaf collecting hobbyist are best friends. For some odd reason,
   GDB has tons of different kinds of leafs and the hobbyist is just
   getting his collection started. The hobbyist, named Foo, often asks
   GDB for a particular kind of leaf, knowing that GDB has it. Since GDB
   is willing to get rid of some of his collection, he sends to Foo the
   leaf every time. Sometimes, when GDB finds an extra leaf, he sends it to
   Foo, even though Foo didn't ask for it. The only problem is, Foo can not
   figure out what kind of leaf he got, since there are several others
   that look almost exactly like it. So Foo spends a large portion of
   the time guessing what kind of leaf he was just given, even though
   GDB could have just put on the envelope the type of leaf that it
   was. Foo can not understand why GDB is so mysterious about the leafs
   he hands out. The end.

hehe, anyways, I'm interested in hearing how you solve the top two
problems.

Thanks,
Bob Rossi

  reply	other threads:[~2004-09-25 20:12 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1095954341.19418.ezmlm@sources.redhat.com>
2004-09-23 18:23 ` Jim Ingham
2004-09-25  1:05   ` Bob Rossi
2004-09-25 19:01     ` Jim Ingham
2004-09-25 20:12       ` Bob Rossi [this message]
2004-09-27 17:39         ` Jim Ingham
2004-09-29  3:00           ` Bob Rossi
2004-09-29 16:13             ` Jim Ingham
2004-09-29 17:27               ` Bob Rossi
2004-09-30 13:26             ` Eli Zaretskii
2004-09-30 16:21               ` Bob Rossi
2004-09-30 16:36                 ` Andrew Cagney
2004-09-30 20:42                   ` Bob Rossi
     [not found] <5733AD9C-0CF7-11D9-8325-000A9569836A@brasko.net>
2004-09-23  0:31 ` Jason Molenda
2004-09-22 13:40 Fabian Cenedese
2004-09-22 13:48 ` Bob Rossi
2004-09-22 14:10   ` Fabian Cenedese
2004-09-22 14:43     ` Bob Rossi
2004-09-22 15:01       ` Fabian Cenedese
2004-09-22 14:58     ` Alain Magloire
2004-09-22 16:18       ` Bob Rossi
2004-09-22 16:59         ` Alain Magloire

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=20040925201242.GA4133@white \
    --to=bob@brasko.net \
    --cc=gdb@sources.redhat.com \
    --cc=jingham@apple.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).