This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH v4 9/9] enable target-async
- From: Tom Tromey <tromey at redhat dot com>
- To: Pedro Alves <palves at redhat dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Mon, 09 Dec 2013 08:57:46 -0700
- Subject: Re: [PATCH v4 9/9] enable target-async
- Authentication-results: sourceware.org; auth=none
- References: <1382464769-2465-1-git-send-email-tromey at redhat dot com> <1382464769-2465-10-git-send-email-tromey at redhat dot com> <52828856 dot 9070904 at redhat dot com> <87li0qve9y dot fsf at fleche dot redhat dot com> <528A2E8B dot 9050300 at redhat dot com> <87r49piu9z dot fsf at fleche dot redhat dot com> <52A5B11A dot 4060900 at redhat dot com>
>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:
>> That is, gdb now emits reason="end-stepping-range". This is a
>> compatible change to the output. This explains the patch: now the
>> !$async case is no longer hit.
Pedro> The question is whether that is actually true on all the other
Pedro> backends/targets that _don't_ know how to async. Like e.g.,
Pedro> Windows.
Thanks, I see what you mean, finally. I'll test it (really everything)
in the new special not-async mode and fix the test case accordingly.
It's an awful irony that trying to remove target-async has actually
apparently made the mode situation worse :-(
Tom