Setting up Solaris GDB builders

Rainer Orth ro@CeBiTec.Uni-Bielefeld.DE
Thu Sep 17 07:34:49 GMT 2026


Hi Mark,

>> * To keep build times in check, I'd like the double ncpus/maxcpus of the
>>   workers to 8.
>
> Set to 8.  Do you still want max_builds=1? That is one build at a
> time.  You could also keep cpus at 4 but set max_builds to 2. So if
> there is a binutils and gdb build pending then they can be done in
> parallel.

true, but I don't expect this to help much.  AFAICS most binutils
commits will trigger gdb builds, too, so having them run in parallel
won't help, while gdb-only builds will be hampered by the reduced
parallelism.

>> * There's no need for 32-bit GDB builders, so we should go for only
>>   gdb-solaris11-amd64 and gdb-solaris11-sparcv9.
>
> OK. I also added try builders.

Fine, thanks.

>> * There are a couple of peculiarities about the builders:
>> 
>> ** They shouldn't include sim.  Right now, it doesn't even build (PR
>>    sim/34536), but even if it did, there's little point, so excluding it
>>    will reduce build time.
>> 
>> ** In a similar vein, the builds should be configured without
>>    --enable-targets=all.  While the build itself has recently been fixed
>>    in response to PR build/34537, I'm primarily interested in a
>>    native-only configuration.
>
> OK added a special gdb_configure_solaris11_step that doesn't include
> --enable-targets=all, but does add --disable-sim.

Excellent.  We can always change that at a later point should the need
arise.

>> ** The PATH for the builders again needs to differ from the binutils
>>    ones: they can and should use the native tools only, i.e. use a PATH
>>    of /usr/gnu/bin:/usr/bin:/usr/sbin.
>
> env PATH for all builders set to /usr/gnu/bin:/usr/bin:/usr/sbin.

Perfect: just the native tools is all they need.

>> Currently, there's one remaining failure, reported as PR testsuite/34535.
>> A patch is currently in review:
>> 
>> 	Handle missing catchpoint support in gdb.base/break.exp [PR34535]
>>         https://sourceware.org/pipermail/gdb-patches/2026-August/229610.html
>>         https://sourceware.org/pipermail/gdb-patches/2026-August/229689.html
>> 
>> Once that's in, the builders will have clean results for the limited set
>> of tests used.
>
> So I assume you want to build only the gdb_test_exp tests like (most)
> other gdb builders.

Exactly: at the moment a full testsuite run is extremely slow with 400+
tests timing out.  I may be able to fix this eventually, but that not
something I expect to happen any time soon.

> I wasn't sure if you wanted to test
> --target_board=native-[extended-]gdbserver
> so that isn't included for now. But can of course be added.

There's no need: gdbserver isn't supported on Solaris anyway.

> I checked in the attached patch. Lets see how that works out.

The first two builds have been unexpectedly smooth.  ISTM that the only
issue keeping them red are a couple of UNRESOLVED tests.  I'd missed
them before in the 3000+ failures of a full gdb make check run,
unfortunately.

I'll try to figure out what's wrong.

Thanks a lot for your help setting this up.

	Rainer

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


More information about the Buildbot mailing list