Hi Andrew,

>>> So maybe DAP testing should be entirely disabled for Solaris?
>>
>> Like just returning 0 from allow_dap_tests on Solaris?  Or doing so for
>> all targets lacking async support?
>
> I'd suggest adding:
>
>   # Return true for targets that support target async,
>   # otherwise return false.
>   proc supports_target_async {} {
>     # ...
>   }
>
> then return 0 from allow_dap_tests for any target that returns false
> from the above.  That would seem better than just having a selective fix
> in the pause.exp file.

that certainly makes the most sense.

>> Here's a breakdown of gdb.dap results on Solaris:
>>
>>       8 ERROR
>>      11 FAIL
>>     713 PASS
>>       8 PATH
>>       8 UNRESOLVED
>>       2 UNSUPPORTED
>>
>> I can't tell if it's still useful this way.
>
> I haven't checked by a lot of these passes are going to be general
> boiler plate stuff.  If DAP support is known to require target async

... which wasn't completely certain as far as I understood Tom...

> then my personal feeling is that we'd be better just skipping those
> tests on Solaris.  There's plenty of testing done on other targets where
> target async is supported.

Right: some of them already do their own checks for async support:

      gdb.base/async.exp
      gdb.base/bg-exec-sigint-bp-cond.exp
      gdb.base/interrupt-noterm.exp

but in those cases, async commands are a crucial part of the tests and I
couldn't easily use the new supports_target_async there.

There are certainly others that aren't handled yet.  Besides, there are
ca. 400 tests that currently time out on Solaris, massively increasing
make check time ;-(  I guess it's a major effort to reduce that number.

>>> Rainer> This might also be a candidate for the gdb-18 branch.
>>>
>>> It's fine by me.
>>
>> Thanks.  I'll way for approval from a release manager then.
>
> It might be worth getting the above changes made first.  If you don't
> have time then let me know and I'll take care of it.

I've now managed to get this working, although it took me some time to
wrap my head around gdb testing procedures.

Here's what I came up with.  The only change on x86-64-pc-linux-gnu was

+PASS: gdb.testsuite/gdb-caching-proc-consistency.exp: supports_target_async: consistency

while on Solaris it fully disabled the gdb.dap tests as expected.

---------------------------------------------------------------------------

As detailed in PR PR dap/34548, the gdb.dap/pause.exp test runs
indefinitely on Solaris.  To allow make check to finish, it needs to be
terminated manually.

Since DAP requires asynchronous execution support, this patch checks for
that and disables all gdb.dap tests if missing.

Tested on x86_64-pc-solaris2.11, sparcv9-sun-solaris2.11, and
x86_64-pc-linux-gnu.

Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=34548

-- 
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University