This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [MI/RFC] Emit ^running via observer.


On Saturday 28 June 2008 14:43:56 Vladimir Prus wrote:

> > ^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.

Should be fixed now. Let me know if you continue to have test failures.

- Volodya


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]