Re: breakpoint commands no more working due to MI front-end

[David Lamy-Charrier <david.lamy@gmail.com>]

Thanks Daniel for the idea, I am going to try it.

But if I am right, mi_execute_command is called to handle MI commands
from the front-end, so it is already too late to execute the commands
associated with the breakpoint.
The commands should have been executed before and the front-end should
even not be notified that GDB stopped and continued, no?

Thanks,
David

On 1/23/06, Daniel Jacobowitz <drow@false.org> wrote:
> On Mon, Jan 23, 2006 at 04:45:51PM +0100, David Lamy-Charrier wrote:
> > Daniel,
> >
> > Thanks for your help.
> > Here attached is a log between Eclipse and GDB.
> > GDB stops on a breakpoint where it is supposed to display a value and
> > then continue.
> > Unfortunately, it seems that it first informs Eclipse that it stops
> > and Eclipse query infos about threads, stack-frame... and the commands
> > attached to the breakpoint are never executed.
> >
> > When GDB stops on a breakpoint with commands associated, does it
> > inform the front-end with MI commands ? if yes, is it after executing
> > the commands or before ?
>
> Looks like breakpoint commands are just broken with MI.  I think it has
> something to do with the event loop; GDB has too many different ones
> still lying around for me to be sure what's going on.  But I think a
> call to bpstat_do_actions in mi_execute_command or
> mi_execute_command_wrapper might do it.
>
> --
> Daniel Jacobowitz
> CodeSourcery
>