public inbox for
 help / color / mirror / Atom feed
From: Steven Boswell II <>
To: "" <>
Subject: New Bugzilla account?
Date: Wed, 19 Jan 2022 18:19:03 +0000 (UTC)	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hello! May I please have a Bugzilla account on
To weaken my case significantly, I don't have a bug report so much as a feature request.I’m in the middle of porting a very large legacy code base from MS Windows to Linux.One outpoint I've run into is in timer_delete(); there's no way to determine when no more callbacks are forthcoming.This makes it impossible to clean up safely after a timer, especially if the value passed in struct sigevent's sigev_value.sival_ptr is dynamically allocated, e.g. a C++ object.The MS Windows API call DeleteTimerQueueTimer(), and even the ancient timeSetEvent(), allow for notification that there will be no forthcoming timer callbacks.It pains me to see Linux not having an answer to anything MS Windows can do, and the fix is easy (though it'll require an updated API, like timer_create2()/timer_delete2() or something.)
Although says to report bugs first to the packagers/distribution, that seems pointless for something like this.


       reply	other threads:[~2022-01-19 18:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2022-01-19 18:19 ` Steven Boswell II [this message]
2022-01-20  9:26   ` Mark Wielaard

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