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 4885C3858C74; Tue,  1 Mar 2022 13:16:50 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4885C3858C74
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug librt/28799] [Feature request] Enhanced
 timer_create()/timer_delete(), for MS Windows parity
Date: Tue, 01 Mar 2022 13:16:50 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: librt
X-Bugzilla-Version: unspecified
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: fweimer at redhat dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: WORKSFORME
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: security-
X-Bugzilla-Changed-Fields: resolution bug_status
Message-ID: <bug-28799-131-6FfzMBuzZp@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-28799-131@http.sourceware.org/bugzilla/>
References: <bug-28799-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
X-BeenThere: glibc-bugs@sourceware.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Glibc-bugs mailing list <glibc-bugs.sourceware.org>
List-Unsubscribe: <https://sourceware.org/mailman/options/glibc-bugs>,
 <mailto:glibc-bugs-request@sourceware.org?subject=unsubscribe>
List-Archive: <https://sourceware.org/pipermail/glibc-bugs/>
List-Help: <mailto:glibc-bugs-request@sourceware.org?subject=help>
List-Subscribe: <https://sourceware.org/mailman/listinfo/glibc-bugs>,
 <mailto:glibc-bugs-request@sourceware.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2022 13:16:50 -0000

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

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |WORKSFORME
             Status|WAITING                     |RESOLVED

--- Comment #3 from Florian Weimer <fweimer at redhat dot com> ---
(In reply to Steven Boswell II from comment #2)
> Although my limited testing shows that, indeed, this allows the timer to =
get
> shut down cleanly, it reveals another problem.
>=20
> Apparently, in the Linux implementation, a new thread is created (and
> quickly destroyed) for every invocation of a callback-based timer,
> accompanied by a flood of "New Thread" and "Thread exited" messages in my
> gdb window. (The timer in question is invoked 40 times per second.)

Thanks for the feedback. I think this is the expected behavior. It's obviou=
sly
not great for high-frequency timers, but it's the simplest way to avoid
unexpected blocking of unrelated timer events.

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