This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: Is gdb script execution intended to work this way in async mode?
- From: Pedro Alves <palves at redhat dot com>
- To: Doug Evans <dje at google dot com>
- Cc: gdb <gdb at sourceware dot org>
- Date: Tue, 25 Mar 2014 11:46:04 +0000
- Subject: Re: Is gdb script execution intended to work this way in async mode?
- Authentication-results: sourceware.org; auth=none
- References: <CADPb22T40jXhHOXiPG7jnHxTXrGEPm=vqZwFMFxGJ+1H4cNwbA at mail dot gmail dot com> <53308FE0 dot 7080200 at redhat dot com>
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