Make Profiling.pmod doc reflect the real state of things.
Profiling: replace deprecated _next and _prev from Profiling.pmod .
The deprecated functions have been replaced by their proper
succesors - Debug.next and Debug.prev.
Merge commit '722771973bd' into patches/lyslyskom22891031
* commit '722771973bd': (6177 commits)
Verify that callablep responses are aligned with reality.
Merge commit '2470270f500c728d10b8895314d8d8b07016e37b' into grubba/typechecker-automap
* commit '2470270f500c728d10b8895314d8d8b07016e37b': (18681 commits)
Removed the old typechecker.
Merge remote-tracking branch 'origin/8.1' into gobject-introspection
Debug.Profiling: _next and _prev have been renamed
Removed trailing spaces.
Merge branch '8.0' into gobject-introspection
Debug.Profiling and Debug.Watchdog
Debug.Profiling can be used to collect and format profiling
It depends on pike being compiled with profiling support.
Debug.Watchdog is a class that can be instanced that ensures the pike
backend is actually running.
If it is not, or if SIGQUIT is received (or print_debug is called) it
will report all thread backtraces and various other debug information
to stderr, and, if the output was triggered by the watchdog, kill the
It is also possible to run the watchdog in a backend-less mode, in
this mode it is up to the application to regularly call the ping()
function in the watchdog.