On Mon, 28 Apr 2025 at 15:02, Thomas Huth <th...@redhat.com> wrote: > > On 28/04/2025 14.59, Alex Bennée wrote: > > Our default build enables debug info which adds hugely to the size of > > the builds as well as the size of cached objects. Disable debug info > > across the board to save space and reduce pressure on the CI system. > > We still have a number of builds which explicitly enable debug and > > related extra asserts like --enable-debug-tcg. > > > > Signed-off-by: Alex Bennée <alex.ben...@linaro.org> > > --- > > .gitlab-ci.d/buildtest-template.yml | 1 + > > 1 file changed, 1 insertion(+) > > > > diff --git a/.gitlab-ci.d/buildtest-template.yml > > b/.gitlab-ci.d/buildtest-template.yml > > index d4f145fdb5..d9e69c3237 100644 > > --- a/.gitlab-ci.d/buildtest-template.yml > > +++ b/.gitlab-ci.d/buildtest-template.yml > > @@ -24,6 +24,7 @@ > > - ccache --zero-stats > > - section_start configure "Running configure" > > - ../configure --enable-werror --disable-docs --enable-fdt=system > > + --disable-debug-info > > Do we have any jobs that might show stack traces in the console output ? > build-oss-fuzz comes to my mind, but that uses a separate script, so we > should be fine there?
If you build with Rust enabled, and the Rust code panics, then you get a Rust backtrace. But I don't know if that cares about debug info to get its backtraces: quite possibly it's an entirely different mechanism. -- PMM
