Created attachment 1203366 [details] reproducer program source gdb crashes on the valgrind gdb_server integration tests causing the valgrind package build to hang in %check. For now the valgrind package has the gdb_server tests disabled with this valgrind.spec snippet: echo ===============TESTING=================== # On arm the gdb integration tests hang for unknown reasons. # When building a scl we might pick a bad gdb. # Only run the main tools tests. # Recent GDB crashes on the gdb_server tests. Disable everywhere for now. #%ifarch %{arm} ./close_fds make nonexp-regtest || : #%else # %if %{is_scl} # ./close_fds make nonexp-regtest || : # %else # ./close_fds make regtest || : # %endif #%endif The gdb crash isn't related to valgrind however. It can be triggered with the attached program and script (derived from the valgrind testcase): $ gcc -g -O0 -o t t.c -lpthread $ gdb ./t < gdb.input
Created attachment 1203367 [details] GDB stdin script
It does not crash on: gdb-7.11.1-75.fc24.x86_64 It does crash on: gdb-7.12-0.11.20160904.fc26.x86_64 That is a regression.
It is now in upstream 7.12 branch so it does not really require 3ACK: [pushed master+7.12] Fix PR 20345 - call_function_by_hand_dummy: Assertion `tp->thread_fsm == &sm->thread_fsm' failed https://sourceware.org/ml/gdb-patches/2016-09/msg00404.html
BTW its testfile is: gdb.base/infcall-input.exp
Brian, would you mind pm_acking this one, please?
gdb-7.12-0.19.20160929.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-cc57295873
gdb-7.12-0.19.20160929.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-2737.html