Re: [RFC] (windows) GDB/MI crash when using "-list-thread-groups --available"

[Pedro Alves <palves at redhat dot com>]

On 05/16/2018 04:46 PM, Simon Marchi wrote:
> On 2018-05-11 12:45, Pedro Alves wrote:
>> After the inferior is started, the Windows target is pushed in the target
>> stack, so there will be a target beneath, either the exec target, or the
>> dummy target directly.  Either of those returns TARGET_XFER_E_IO for
>> this target object.
>>
>> The issue here is that before the inferior is started, the
>> Windows target is not pushed on the target stack.
>> See target_get_osdata.
> 
> Ah ok, so the target is used without being pushed?  I didn't know it was possible.

Yeah.  A few methods can be called like that.  target_ops::create_inferior
for instance, is called before the target is pushed, and the implementation
of that method is responsible for pushing itself on the stack on success.

> 
>>> which provides the list of available processes on Windows?
>>
>> I don't think the feature works at all on Windows.  It's probably
>> returning an empty list of processes.
> 
> But Joel reported that the test case fails due to the expect buffer being full, so the list must not be empty...  we'll need clarifications from him :)

The reported failure was on GNU/Linux, not Windows.  :-)

Thanks,
Pedro Alves