Wolfgang Hommel

Sorry, not yet. It is only known to affect bash so far (i.e., it does not seem to be a generic problem), and I didn't take the time to look...

jemalloc compatibility is a long-standing problem (see various issues here) and despite several attempts there currently is nothing more we can do on libfaketime's end until some minor changes are...

I agree this is useful, but wonder how exactly you want libfaketime to support that more directly? Since the faketime values can already be changed during run-time, it is straight-forward...

libfaketime's README has a few points about running Java programs. Do none of the settings described there work?

Please try using the file-based mechanism for other processes to make sure it basically works on your system and only fails with dotnet. I don't know how libfaketime could lock...

More recent macOS versions do not allow dynamic library injection by default, even for non-root processes. You'll have to consider tweaking the system's security settings, and since this has system-wide...

My first guess is that changes made to the environment variable are not picked up by programs sent into the background previously. Have you tried, e.g., with ```FAKETIME_TIMESTAMP_FILE```? Other than...

libfaketime does not keep track of opened files, created timers, and so on. If you call ```timerfd_settime``` also in your "Main event loop", changes to the speed factor will be...