https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90636
--- Comment #5 from Dr. Thomas Orgis <thomas.or...@uni-hamburg.de> --- I traced it down to the gcc build process not applying the -g flag consistently. In my build log, I see the respective objects being built two times (not sure in which directory the second one happens, as the build is parallel and needs enough time as it is …). On the second time, the build includes '-g -O2'. On the first time not (only my own CFLAGS in case I had some set). Same for ttest and ttest_alloc. When I enter the build tree and remove the object files, remaking them does include the correct flags including -g and the testsuite of libbacktrace passes. I bet there is a number of people more intimate with the gcc build system, hopefully able to discern why an intermediate build with missing -g happens. I issue a default bootstrap build with 'make -j8'.
