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: RFC: MI output during program execution


> Note that for a truly asynchronous target, what you get is:

> (gdb)
> -exec-continue
> ^running
> (gdb)
> -exec-status
> ^done,status="running"
> (gdb)
> -exec-interrupt
> ^done,reason="signal-received",signal-name="SIGINT",signal- meaning="Interrupt",thread-id="1"
> (gdb)

> Or something like that... So in that case the ^running really is the
> equivalent of the ^done...

I don't really mind if it is ^running or *running, I just want GDB to issue
notification when the inferior starts or stops running after a CLI command is
executed.  Currently I can't tell when to update the UI when such commands are
issued through the GUD buffer.  Daniel suggested this was a different case to
breakpoint-changed or thread-changed but I think it requires a similar
solution.

Nick


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