Setting up Solaris GDB builders
Rainer Orth
ro@CeBiTec.Uni-Bielefeld.DE
Sun Aug 23 09:43:48 GMT 2026
When setting up the Solaris binutils workers/builders, I mentioned the
possibility to also create matching GDB builders. GDB is now almost
ready for this.
Here's the setup I envision:
* We can just reuse the existing solaris11-sparcv9 and solaris11-amd64
workers. Unlike what I thought initially, there's no need to set up
separate workers for gdb.
* To keep build times in check, I'd like the double ncpus/maxcpus of the
workers to 8.
* There's no need for 32-bit GDB builders, so we should go for only
gdb-solaris11-amd64 and gdb-solaris11-sparcv9.
* 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.
** 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.
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.
Thanks again for your help.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
More information about the Buildbot
mailing list