Re: MI output command error

Nick Roberts
2005-03-13T23:33:42Z

> > At the moment I have some time, so I can offer to try. I will need some
> > hand holding though. What files should I look at, and what behaviour
> > would you expect?
>
> Have I mentioned that I don't know anything about MI? :-) I'm afraid I
> have no advice. I would expect -exec-interrupt to send a signal to the
> target process, just like GDB's SIGINT handler does. Which isn't
> perfect, but generally works.

OK. Theres an example in the manual that I can follow:

(gdb)
111-exec-continue
111^running

(gdb)
222-exec-interrupt
222^done
(gdb)
111*stopped,signal-name="SIGINT",signal-meaning="Interrupt",
frame={addr="0x00010140",func="foo",args=[],file="try.c",line="13"}
(gdb)

However, with it looking like Andrew has gone AWOL, who would review any such
patches?

Nick