[Bug gdb/29965] [gdb] FAIL: gdb.threads/process-exit-status-is-leader-exit-status.exp: iteration=1: continue (the program exited)

["cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=29965

--- Comment #9 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Simon Marchi <simark@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=ea186080fe2b94b21f3ac8ad7941948211d5e67a

commit ea186080fe2b94b21f3ac8ad7941948211d5e67a
Author: Simon Marchi <simon.marchi@efficios.com>
Date:   Thu Sep 7 21:53:55 2023 -0400

    gdb/testsuite: add xfail for gdb/29965 in
gdb.threads/process-exit-status-is-leader-exit-status.exp

    Bug 29965 shows on a Linux kernel >= 6.1, that test fails consistently
    with:

        FAIL: gdb.threads/process-exit-status-is-leader-exit-status.exp:
iteration=0: continue (the program exited)
        ...
        FAIL: gdb.threads/process-exit-status-is-leader-exit-status.exp:
iteration=9: continue (the program exited)

    This is due to a change in Linux kernel behavior [1] that affects
    exactly what this test tests.  That is, if multiple threads (including
    the leader) call SYS_exit, the exit status of the process should be the
    exit status of the leader.  After that change in the kernel, it is no
    longer the case.

    Add an xfail in the test, based on the Linux kernel version.  The goal
    is that if a regression is introduced in GDB regarding this feature, it
    should be caught if running on an older kernel where the behavior was
    consistent.

    [1] https://bugzilla.suse.com/show_bug.cgi?id=1206926

    Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=29965
    Change-Id: If6ab7171c92bfc1a3b961c7179e26611773969eb
    Approved-By: Tom de Vries <tdevries@suse.de>

-- 
You are receiving this mail because:
You are on the CC list for the bug.