Hi! I'd like to highlight the following report: On Thu, 11 Apr 2019 00:50:50 -0400, sergiodj+buildbot@sergiodj.net wrote: > Buildslave: > fedora-x86-64-4 > > Full Build URL: > > > Commit(s) tested: > 9d1447e09d4aa673826039321163b5a684e8e043 > > Author(s) (in the same order as the commits): > Sergio Durigan Junior > > Subject: > Destroy allocated values when exiting GDB > > Testsuite log (gdb.sum and gdb.log) URL(s): > > > *** Diff to previous build *** > ============================ > PASS -> FAIL: gdb.server/abspath.exp: continue to main > PASS -> FAIL: gdb.server/connect-without-multi-process.exp: multiprocess=auto: continue to main > PASS -> FAIL: gdb.server/connect-without-multi-process.exp: multiprocess=off: continue to main > PASS -> FAIL: gdb.server/ext-run.exp: kill > PASS -> UNRESOLVED: gdb.server/ext-run.exp: load new file without any gdbserver inferior > PASS -> FAIL: gdb.server/ext-wrapper.exp: kill > PASS -> FAIL: gdb.server/reconnect-ctrl-c.exp: first: stop with control-c > PASS -> FAIL: gdb.server/server-kill.exp: continue to breakpoint: after server_pid assignment > PASS -> FAIL: gdb.server/server-run.exp: continue to main > PASS -> FAIL: gdb.server/solib-list.exp: non-stop 1: sharedlibrary > PASS -> FAIL: gdb.server/stop-reply-no-thread.exp: continue to main > PASS -> FAIL: gdb.server/wrapper.exp: continue to marker > PASS -> KFAIL: gdb.threads/process-dies-while-handling-bp.exp: non_stop=on: cond_bp_target=1: inferior 1 exited > ============================ > > > *** Complete list of XFAILs for this builder *** > > To obtain the list of XFAIL tests for this builder, go to: > > > > You can also see a pretty-printed version of the list, with more information > about each XFAIL, by going to: > > In d970ee2bae1925bb9265d37adef0b92e2678d666..02e902e1a1ec7b74125f329b3faef1992efb6d51 (that is, basically, last week) I'm too seeing a good number of 'gdb.server' testsuite regressions in native i686-pc-linux-gnu testing: Running [...]/gdb/testsuite/gdb.server/abspath.exp ... {+FAIL: gdb.server/abspath.exp: continue to main+} Running [...]/gdb/testsuite/gdb.server/connect-stopped-target.exp ... Running [...]/gdb/testsuite/gdb.server/connect-with-no-symbol-file.exp ... Running [...]/gdb/testsuite/gdb.server/connect-without-multi-process.exp ... {+FAIL: gdb.server/connect-without-multi-process.exp: multiprocess=off: continue to main+} {+FAIL: gdb.server/connect-without-multi-process.exp: multiprocess=auto: continue to main+} Running [...]/gdb/testsuite/gdb.server/ext-attach.exp ... Running [...]/gdb/testsuite/gdb.server/ext-restart.exp ... {+FAIL: gdb.server/ext-restart.exp: run to main+} {+FAIL: gdb.server/ext-restart.exp: restart: run to main+} Running [...]/gdb/testsuite/gdb.server/ext-run.exp ... {+FAIL: gdb.server/ext-run.exp: continue to main+} Running [...]/gdb/testsuite/gdb.server/ext-wrapper.exp ... {+FAIL: gdb.server/ext-wrapper.exp: run to marker+} {+FAIL: gdb.server/ext-wrapper.exp: print d+} {+FAIL: gdb.server/ext-wrapper.exp: restart: run to marker+} {+FAIL: gdb.server/ext-wrapper.exp: restart: print d+} Running [...]/gdb/testsuite/gdb.server/extended-remote-restart.exp ... Running [...]/gdb/testsuite/gdb.server/file-transfer.exp ... Running [...]/gdb/testsuite/gdb.server/no-thread-db.exp ... {+FAIL: gdb.server/no-thread-db.exp: continue to breakpoint: after tls assignment+} Running [...]/gdb/testsuite/gdb.server/non-existing-program.exp ... Running [...]/gdb/testsuite/gdb.server/reconnect-ctrl-c.exp ... {+FAIL: gdb.server/reconnect-ctrl-c.exp: first: stop with control-c+} {+FAIL: gdb.server/reconnect-ctrl-c.exp: second: stop with control-c+} Running [...]/gdb/testsuite/gdb.server/run-without-local-binary.exp ... {+FAIL: gdb.server/run-without-local-binary.exp: run test program until the end+} Running [...]/gdb/testsuite/gdb.server/server-connect.exp ... Running [...]/gdb/testsuite/gdb.server/server-exec-info.exp ... Running [...]/gdb/testsuite/gdb.server/server-kill.exp ... {+FAIL: gdb.server/server-kill.exp: continue to breakpoint: after server_pid assignment+} {+FAIL: gdb.server/server-kill.exp: tstatus+} Running [...]/gdb/testsuite/gdb.server/server-mon.exp ... Running [...]/gdb/testsuite/gdb.server/server-run.exp ... {+FAIL: gdb.server/server-run.exp: continue to main+} Running [...]/gdb/testsuite/gdb.server/solib-list.exp ... {+FAIL: gdb.server/solib-list.exp: non-stop 0: continue+} {+FAIL: gdb.server/solib-list.exp: non-stop 0: p libvar+} {+FAIL: gdb.server/solib-list.exp: non-stop 1: continue+} {+FAIL: gdb.server/solib-list.exp: non-stop 1: p libvar+} Running [...]/gdb/testsuite/gdb.server/stop-reply-no-thread.exp ... {+FAIL: gdb.server/stop-reply-no-thread.exp: continue to main+} {+Running [...]/gdb/testsuite/gdb.server/sysroot.exp ...+} {+FAIL: gdb.server/sysroot.exp: sysroot=local: continue to main+} {+FAIL: gdb.server/sysroot.exp: sysroot=local: continue to printf+} {+FAIL: gdb.server/sysroot.exp: sysroot=remote: continue to main+} {+FAIL: gdb.server/sysroot.exp: sysroot=remote: continue to printf+} Running [...]/gdb/testsuite/gdb.server/unittest.exp ... Running [...]/gdb/testsuite/gdb.server/wrapper.exp ... {+FAIL: gdb.server/wrapper.exp: continue to marker+} {+FAIL: gdb.server/wrapper.exp: print d+} These generally seem to be because the "Program received signal SIGSEGV, Segmentation fault". Not any further bisected, or analyzed. Grüße Thomas