From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
	id A23BA385771A; Thu, 15 Jun 2023 19:36:23 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A23BA385771A
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1686857783;
	bh=20sYHwhrgnAWC8Au/M1OMIZF07a03eJfDvlr/IQeYMo=;
	h=From:To:Subject:Date:From;
	b=KKS3b2pIqS7Qw1bGe7lUqD/ruKt5AVfeBkOXsIY0QBEjvB8KMBV5fj51Z9KQMrOQk
	 fnn24xhrDzuTjg6XQZAEp7uxUZmWjeruj3APhleu4Oe3Yf5Thv/qf5GlXsGp1Ahxfp
	 GiQVefo2SnOYvwFQeYJ6eiv+Np1Kmtc3gp5Ad14M=
From: "stsp at users dot sourceforge.net"
 <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/30558] New: SIGEV_THREAD is badly implemented
Date: Thu, 15 Jun 2023 19:36:23 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: libc
X-Bugzilla-Version: 2.37
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: stsp at users dot sourceforge.net
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status
 bug_severity priority component assigned_to reporter cc target_milestone
Message-ID: <bug-30558-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <glibc-bugs.sourceware.org>

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

            Bug ID: 30558
           Summary: SIGEV_THREAD is badly implemented
           Product: glibc
           Version: 2.37
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: libc
          Assignee: unassigned at sourceware dot org
          Reporter: stsp at users dot sourceforge.net
                CC: drepper.fsp at gmail dot com
  Target Milestone: ---

SIGEV_THREAD seems to currently create
and destroy the thread per every timer
tick. In gdb I have the flood of

[Thread 0x7fff698b56c0 (LWP 1304252) exited]
[New Thread 0x7fff698b56c0 (LWP 1304253)]
[Thread 0x7fff698b56c0 (LWP 1304253) exited]
[New Thread 0x7fff698b56c0 (LWP 1304254)]
[Thread 0x7fff698b56c0 (LWP 1304254) exited]

messages, and under freebsd gdb simply asserts out.

While definitely not a bug, I think it would
be very good both for debugability and performance
to have just 1 thread per SIGEV_THREAD timer,
that gets destroyed only together with the timer.

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