https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119694
Simon Sobisch <simonsobisch at gnu dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |simonsobisch at gnu dot org
--- Comment #9 from Simon Sobisch <simonsobisch at gnu dot org> ---
If you have access to the memory of the process you can adjust the return value
from time functions before they are used. If you start the process you can most
often do LD_PRELOAD - and return another timestamp.
If you have admin rights or run the program in a container, you can adjust the
system time...
And you likely know about SOURCE_DATE_EPOCH - a variable that's globally used
to produce reproducible timestamps and therefore binaries...
At least these were my main thoughts when considering the addition of
COB_CURRENT_DATE to GnuCOBOL.
Note: if that's implemented on your side similar to how libcob does, then it
can also be used to "fake" the right timezone or nanoseconds, especially on
ancient systems that don't support them - but then... other than GnuCOBOL you
may not need to build on those.
