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: Fri, 21 Feb 2014 13:23:07 -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> <87ob4qf24l dot fsf at fleche dot redhat dot com>
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.
Tom> Thanks, I see what you mean, finally. I'll test it (really everything)
Tom> in the new special not-async mode and fix the test case accordingly.
I patched the test case in question (mi-cli.exp) to fix this problem.
Then I patched gdb to disable the new "maint set target-async" by
default (and to make "set target-async" enable this mode as well ... a
hack only needed when doing this kind of test) and re-ran the test
suite. This passed. So, I don't think there should be any other bugs
that will bite on a non-target-async system. That said, I will test the
next revision of the series on AIX, which is truly not-async.
Tom