[PATCH v2 00/25] Towards great frontend GDB consoles

Pedro Alves palves@redhat.com
Mon Mar 21 19:12:00 GMT 2016


On 03/21/2016 07:06 PM, Marc Khouzam wrote:

>> From: Pedro Alves [palves@redhat.com]

>>> 2- Using 'interpreter-exec mi" in the CLI console confuses GDB
>>>      To reproduce from a shell
>>>      - start GDB in CLI mode
>>>      - give a "new-ui mi" command to start an MI channel
>>>      - start running the inferior => *stopped/*running events are on the MI channel
>>>      - in the CLI send command interpreter-exec mi ""
>>>      - step or resume
>>>      => *stopped/*running events are now on the CLI channel and not the MI one
>>
>> I can reproduce this.
>>
>> This may be related to the fact that MI's code still has a bunch of
>> globals that I hadn't made per-UI, thinking that that would be sufficient
>> for the use case at hand.  While annoying, I wouldn't expect a
>> regular user / script to be issuing MI commands, right?
> 
> Yes, I guess I'm one of the rare people that use interpreter-exe mi :)

:-)

> So, making this work is not urgent at all.  But I am a little worried that
> if the user does issue such a command, the eclipse session stops
> working (as it misses the MI events).  

Indeed.

> Would it be hard to disable
> the problematic command when 'new-ui' has been used?

Hmm, probably not.  I don't know yet whether it'd be hard to
fix properly, but I'll take a look first before taking that route.

Thanks,
Pedro Alves



More information about the Gdb-patches mailing list