Is gdb script execution intended to work this way in async mode?

Is gdb script execution intended to work this way in async mode?

[Doug Evans]

Hi.
If I source a script in target-async mode, non-asynchronous execution
commands "finish" immediately in the sense that the following command
in the script is done before the previous command has completed (in
the expected sense - the command completes immediately, so to speak,
but continuations are registered to perform the rest of the command,
e.g. to keep stepping until a "next" has fully completed).

I hope this is a bug.

int
main ()
{
  while (1)
    sleep (1);
}

set target-async on
file a.out
start
source foo.gdb

foo.gdb:
next
next

-->

foo.gdb:2: Error in sourced command file:

Cannot execute this command while the selected thread is running.

Turn on the following for better visualization:
set debug infrun 1
set trace-commands on

The second "next" command is executed before the continuations that
implement the completion of the previous "next" command have, umm,
completed.

Re: Is gdb script execution intended to work this way in async mode?

[Pedro Alves]

On 03/22/2014 12:13 AM, Doug Evans wrote:
> Hi.
> If I source a script in target-async mode, non-asynchronous execution
> commands "finish" immediately in the sense that the following command
> in the script is done before the previous command has completed (in
> the expected sense - the command completes immediately, so to speak,
> but continuations are registered to perform the rest of the command,
> e.g. to keep stepping until a "next" has fully completed).
> 
> I hope this is a bug.

Yes.  set target-async on/off is supposed to be transparent.
The only difference should be that "set target-async on" enables more
features.  I thought this was fixed, but looks like not...
Sounds like we forget to clear interpreter_async while running
the script?

-- 
Pedro Alves

Re: Is gdb script execution intended to work this way in async mode?

[Pedro Alves]

On 03/24/2014 08:04 PM, Pedro Alves wrote:
> On 03/22/2014 12:13 AM, Doug Evans wrote:
>> Hi.
>> If I source a script in target-async mode, non-asynchronous execution
>> commands "finish" immediately in the sense that the following command
>> in the script is done before the previous command has completed (in
>> the expected sense - the command completes immediately, so to speak,
>> but continuations are registered to perform the rest of the command,
>> e.g. to keep stepping until a "next" has fully completed).
>>
>> I hope this is a bug.
> 
> Yes.  set target-async on/off is supposed to be transparent.
> The only difference should be that "set target-async on" enables more
> features.  I thought this was fixed, but looks like not...
> Sounds like we forget to clear interpreter_async while running
> the script?

Yes, that's what's happening.  I'm testing a fix.

-- 
Pedro Alves