works ok for me for a long time Thanks
ping
It's still causing problems with jemalloc-enabled applications, https://github.com/wolfcw/libfaketime/issues/130
If I read the bug report properly... that bug is not fixable? :/ (upstream even closed it)
Unable to check for sanity: > no match for package: sys-libs/libfaketime-0.9.8
libfaketime-0.9.6 has the bug https://github.com/wolfcw/libfaketime/issues/127 which is fixed in 0.9.9
Keywords are not fully specified and arches are not CC-ed for the following packages: - =sys-libs/libfaketime-0.9.9
Issue 130 is still a problem. But I will backport the fix https://github.com/wolfcw/libfaketime/commit/bb635e4367adcac2c1517a698799a60a2bf86e83 for the problem we experienced today in our Gentoo workshop to our stable version. Thank you for the link!
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5eda431bfc0b8afd8f15fb3127cd32caf93ff120 commit 5eda431bfc0b8afd8f15fb3127cd32caf93ff120 Author: Thomas Deutschmann <whissi@gentoo.org> AuthorDate: 2021-11-21 03:17:49 +0000 Commit: Thomas Deutschmann <whissi@gentoo.org> CommitDate: 2021-11-21 03:18:16 +0000 sys-libs/libfaketime: treat unknown clock_ids like CLOCK_REALTIME Backport of commit bb635e4367adcac2c1517a698799a60a2bf86e83 upstream. Bug: https://bugs.gentoo.org/733590 Package-Manager: Portage-3.0.28, Repoman-3.0.3 Signed-off-by: Thomas Deutschmann <whissi@gentoo.org> ...eat-unknown-clock_ids-like-CLOCK_REALTIME.patch | 35 ++++++++++++++++++++++ ...0.9.6-r3.ebuild => libfaketime-0.9.6-r4.ebuild} | 2 ++ 2 files changed, 37 insertions(+)
The "intercepting malloc" problem is a complex one and it's not going to be specific to jemalloc. I don't think it's really worth holding up stabilisation of this forever on. We can consider keeping old versions around though, I guess.
