Re: Calling inferior functions and MI notification

[Vladimir Prus <ghost@cs.msu.su>]

Pawel Piech wrote:

> Vladimir Prus wrote:
>> Pawel Piech wrote:
>>
>>   
>>> It would be helpful if *running event included a "reason" field.  IDE's
>>> ususally track the command they just sent to determine the reason for
>>> resume event, but as it's an out-of-band record there is a possibility
>>> of a race condition which could break the IDE assumption.
>>>     
>>
>> Hello Pawel,
>>
>> can you clarify what the 'reason' field should contain? I think that in
>> general, reporting the command that caused the run might be impossible.
>>
>>   
> Too bad, because that's what I had in mind....  Like I said, IDE's
> including Eclipse usually solve this problem on their own, though the
> solution is theoretically susceptible to a race condition in cases where
> multiple interfaces are used to interact with GDB simultaneously.

In what cases associating "*running" with a command is important? You
still get "^running", so you know what the command started something.
The "*running" can be used to update the state of the threads in UI.

I'm actually thinking of making -thread-info report the operation that
each running thread executes, like "step" or "finish" -- when that
information is available.

- Volodya