From: Eli Zaretskii <eliz@gnu.org>
To: Marc Khouzam <marc.khouzam@ericsson.com>
Cc: stanshebs@earthlink.net, gdb-patches@sourceware.org
Subject: Re: GDB/MI and ">" prompts
Date: Tue, 08 May 2012 18:51:00 -0000 [thread overview]
Message-ID: <83obpy1pad.fsf@gnu.org> (raw)
In-Reply-To: <F7CE05678329534C957159168FA70DEC57968C02F5@EUSAACMS0703.eamcs.ericsson.se>
> From: Marc Khouzam <marc.khouzam@ericsson.com>
> Date: Tue, 8 May 2012 11:39:25 -0400
>
> I tried Eli's patch with Eclipse and I didn't see any problems.
>
> I was concerned that changing to the CLI interpreter for a while
> could make us lose some MI events, but it does not seem to be
> the case. For example, I tried running a thread that will hit
> a breakpoint in 5 seconds; I then got into the 'commands' secondary
> prompt and waited for the 5 seconds to pass. The *stopped event
> was not reported until I sent the 'end' command and got out
> of the secondary prompt. This is the behavior with and without
> Eli's patch. So it seems MI events are buffered in that case,
> and switching to the CLI interpreter does not make use lose that
> event.
>
> So, it seems ok for an Eclipse perspective.
Thanks!
prev parent reply other threads:[~2012-05-08 18:51 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
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 [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=83obpy1pad.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=marc.khouzam@ericsson.com \
--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