public inbox for
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot" <>
Subject: [Bug gdb/29965] [gdb] FAIL: gdb.threads/process-exit-status-is-leader-exit-status.exp: iteration=1: continue (the program exited)
Date: Tue, 26 Sep 2023 18:21:55 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

--- Comment #9 from cvs-commit at gcc dot <cvs-commit at gcc dot> ---
The master branch has been updated by Simon Marchi <>:;h=ea186080fe2b94b21f3ac8ad7941948211d5e67a

commit ea186080fe2b94b21f3ac8ad7941948211d5e67a
Author: Simon Marchi <>
Date:   Thu Sep 7 21:53:55 2023 -0400

    gdb/testsuite: add xfail for gdb/29965 in

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

        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


    Change-Id: If6ab7171c92bfc1a3b961c7179e26611773969eb
    Approved-By: Tom de Vries <>

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

      parent reply	other threads:[~2023-09-26 18:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-05 12:30 [Bug gdb/29965] New: " vries at gcc dot
2023-01-05 12:30 ` [Bug gdb/29965] " vries at gcc dot
2023-01-05 12:36 ` vries at gcc dot
2023-01-05 12:37 ` vries at gcc dot
2023-01-05 12:50 ` vries at gcc dot
2023-01-05 12:56 ` vries at gcc dot
2023-01-05 13:14 ` vries at gcc dot
2023-01-05 13:25 ` vries at gcc dot
2023-01-06 11:21 ` vries at gcc dot
2023-06-22 13:45 ` iii at linux dot
2023-09-12 17:57 ` simon.marchi at polymtl dot ca
2023-09-26 18:21 ` cvs-commit at gcc dot [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).