Branch: Tag:

2019-11-03

2019-11-03 18:43:44 by Mateusz Krawczuk <krawczukmat@gmail.com>

Make Profiling.pmod doc reflect the real state of things.

2019-11-02

2019-11-02 18:31:04 by Mateusz Krawczuk <krawczukmat@gmail.com>

Profiling: replace deprecated _next and _prev from Profiling.pmod .

The deprecated functions have been replaced by their proper
succesors - Debug.next and Debug.prev.

2019-03-19

2019-03-19 12:33:55 by Henrik Grubbström (Grubba) <grubba@grubba.org>

Merge commit '722771973bd' into patches/lyslyskom22891031

* commit '722771973bd': (6177 commits)
Verify that callablep responses are aligned with reality.
...

2019-03-14

2019-03-14 10:39:03 by Henrik Grubbström (Grubba) <grubba@grubba.org>

Merge commit '2470270f500c728d10b8895314d8d8b07016e37b' into grubba/typechecker-automap

* commit '2470270f500c728d10b8895314d8d8b07016e37b': (18681 commits)
Removed the old typechecker.
...

2018-11-03

2018-11-03 14:21:37 by Marcus Comstedt <marcus@mc.pp.se>

Merge remote-tracking branch 'origin/8.1' into gobject-introspection

2017-11-21

2017-11-21 22:04:05 by Arne Goedeke <el@laramies.com>

Debug.Profiling: _next and _prev have been renamed

2015-05-26

2015-05-26 10:33:42 by Martin Nilsson <nilsson@opera.com>

Removed trailing spaces.

2014-02-14

2014-02-14 21:09:25 by Martin Nilsson <nilsson@opera.com>

Simplified dependencies.

2014-01-05

2014-01-05 15:14:13 by Marcus Comstedt <marcus@mc.pp.se>

Merge branch '8.0' into gobject-introspection

2013-12-21

2013-12-21 20:20:43 by Martin Nilsson <nilsson@opera.com>

Added #pike

2013-10-28

2013-10-28 17:20:51 by Martin Nilsson <nilsson@opera.com>

doc fixes.

2013-10-28 16:50:22 by Per Hedbor <ph@opera.com>

Debug.Profiling and Debug.Watchdog

Debug.Profiling can be used to collect and format profiling
information.

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

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.