Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stan Shebs <stanshebs@earthlink.net>
Cc: gdb-patches@sourceware.org
Subject: Re: GDB/MI and ">" prompts
Date: Mon, 30 Apr 2012 17:18:00 -0000	[thread overview]
Message-ID: <83k40x5eq4.fsf@gnu.org> (raw)
In-Reply-To: <4F9EBD0D.2090701@earthlink.net>

> Date: Mon, 30 Apr 2012 09:25:49 -0700
> From: Stan Shebs <stanshebs@earthlink.net>
> 
> It seems logically correct... Did you try Eclipse?  This is the kind of 
> thing that CDT's MI and console bits can be sensitive to, even though 
> it's not supposed to be. :-)  If you haven't tried it, doing some 
> breakpoint commands (both from breakpoint window and console window) 
> with any recent released Eclipse should be a sufficient sniff test.
> 
> If Eclipse is good, then this is OK to commit.

Thanks.  No, I didn't try Eclipse, and I don't have it handy.  Perhaps
someone else could.


  reply	other threads:[~2012-04-30 17:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <83vckviv3b.fsf@gnu.org>
     [not found] ` <20120419154853.GM25623@adacore.com>
     [not found]   ` <83sjfzitxx.fsf@gnu.org>
     [not found]     ` <83r4vjitnj.fsf@gnu.org>
     [not found]       ` <20120419185329.GO25623@adacore.com>
     [not found]         ` <83mx67ikxm.fsf@gnu.org>
2012-04-22 16:52           ` Eli Zaretskii
2012-04-28 14:54             ` Eli Zaretskii
2012-04-30 16:26               ` Joel Brobecker
2012-04-30 16:55               ` Stan Shebs
2012-04-30 17:18                 ` Eli Zaretskii [this message]
2012-05-02 15:56                   ` Marc Khouzam
2012-05-02 17:04                     ` Eli Zaretskii
2012-05-08 15:39                 ` Marc Khouzam
2012-05-08 15:51                   ` Joel Brobecker
2012-05-08 18:51                     ` Eli Zaretskii
2012-05-08 18:51                   ` 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=83k40x5eq4.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=stanshebs@earthlink.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