public inbox for
help / color / mirror / Atom feed
From: "vries 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: Thu, 05 Jan 2023 12:56:17 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

--- Comment #5 from Tom de Vries <vries at gcc dot> ---
This linux kernel commit (first include in release v6.1.0) looks interesting:
commit d80f7d7b2c75c5954d335dffbccca62a5002c3e0
Author: Eric W. Biederman <>
Date:   Tue Jun 21 14:38:52 2022 -0500

    signal: Guarantee that SIGNAL_GROUP_EXIT is set on process exit

    Track how many threads have not started exiting and when the last
    thread starts exiting set SIGNAL_GROUP_EXIT.

    This guarantees that SIGNAL_GROUP_EXIT will get set when a process
    exits.  In practice this achieves nothing as glibc's implementation of
    _exit calls sys_group_exit then sys_exit.  While glibc's implemenation
    of pthread_exit calls exit (which cleansup and calls _exit) if it is
    the last thread and sys_exit if it is the last thread.

    This means the only way the kernel might observe a process that does
    not set call exit_group is if the language runtime does not use glibc.

    With more cleanups I hope to move the decrement of quick_threads

    Signed-off-by: "Eric W. Biederman" <>


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

  parent reply	other threads:[~2023-01-05 12:56 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 [this message]
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

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).