From: Vladimir Prus <vladimir@codesourcery.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Nick Roberts <nickrob@snap.net.nz>, gdb-patches@sources.redhat.com
Subject: Re: [MI/RFC] Emit ^running via observer.
Date: Sat, 28 Jun 2008 11:34:00 -0000 [thread overview]
Message-ID: <200806281443.57315.vladimir@codesourcery.com> (raw)
In-Reply-To: <20080626160309.GA17512@caradoc.them.org>
On Thursday 26 June 2008 20:03:09 Daniel Jacobowitz wrote:
> On Thu, Jun 26, 2008 at 07:58:05PM +0400, Vladimir Prus wrote:
> > On Thursday 26 June 2008 07:20:14 Nick Roberts wrote:
> > > > I've checked in the following, which differs from original by extra test
> > > > strictness.
> > >
> > > Thanks.
> > >
> > > > Further, I've converted mi-async.exp to use the helper
> > > > functions. Nick, as it stands now it does not seem that mi-async.exp tests
> > > > async behaviour at all -- it merely changes that we get ^running for CLI
> > > > commands, and we get that in both sync and async mode. Do you think it
> > > > worthwhile to rename the test or move its content somewhere else?
> > >
> > > The tests appear to fail now.
> >
> > Which tests? With unmodified CVS state, all MI tests pass for me both in sync
> > and async mode. But indeed, if I make mi-async.exp not force async mode, it
> > starts to fail....
>
> Not for me.
>
> (gdb)
> start
> &"start\n"
> ~"Temporary breakpoint 1 at 0x400635: file /space/fsf/commit/src/gdb/testsuite/gdb.mi/basics.c, line 62.\n"
> ~"Starting program: /space/fsf/x86-64/commit-gdb/gdb/testsuite/gdb.mi/basics \n"
> =thread-created,id="1"
> ^running
> *running,thread-id="all"
> *stopped,reason="breakpoint-hit",disp="del",bkptno="1",thread-id="1",frame={addr="0x0000000000400635",func="main",args=[],file="/space/fsf/commit/src/gdb/testsuite/gdb.mi/basics.c",fullname="/space/fsf/commit/src/gdb/testsuite/gdb.mi/basics.c",line="62"}
> FAIL: gdb.mi/mi-async.exp: start: send
The test expects (gdb) after *running. I don't actually understand how it can not be
output -- the command is handled by mi_execute_command, which prints prompts at the
end. Ah wait, except for this early exit path:
if (args.action == EXECUTE_COMMAND_SUPPRESS_PROMPT)
/* The command is executing synchronously. Bail out early
suppressing the finished prompt. */
return;
and then:
==20541== Conditional jump or move depends on uninitialised value(s)
==20541== at 0x80DCD38: mi_execute_command (mi-main.c:1138)
I'll fix this shortly -- one way or another.
- Volodya
next prev parent reply other threads:[~2008-06-28 10:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-13 22:01 Vladimir Prus
2008-06-20 6:53 ` Nick Roberts
2008-06-25 15:04 ` Vladimir Prus
2008-06-26 13:33 ` Nick Roberts
2008-06-26 18:54 ` Vladimir Prus
2008-06-26 19:34 ` Daniel Jacobowitz
2008-06-28 11:34 ` Vladimir Prus [this message]
2008-06-28 16:35 ` Vladimir Prus
2008-06-27 6:58 ` Nick Roberts
2008-06-27 11:58 ` Vladimir Prus
2008-06-28 5:49 ` Nick Roberts
2008-06-28 9:41 ` Vladimir Prus
2008-06-28 10:16 ` Nick Roberts
2008-06-28 10:44 ` Vladimir Prus
2008-06-29 2:40 ` Nick Roberts
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=200806281443.57315.vladimir@codesourcery.com \
--to=vladimir@codesourcery.com \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=nickrob@snap.net.nz \
/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