Alexander Larsson bef9efd0a9 Initial support for dtrace and systemtap ... This adds static markers for dtrace, which are also usable by systemtap. Additionally it adds a tapset for systemtap that makes it easier to use the static markers. These are enabled by default. This initial set of probes is rather limited: * allocation and free using g_malloc & co * allocation and free using g_slice * gquark name tracking (useful for converting quarks to strings in probes) Notes on naming: Its traditional with dtrace to use probe names with dashes as delimiter (slice-alloc). Since dashes are not usable in identifiers the C code uses double underscores (slice__alloc) which is converted to dashes in the UI. We follow this for the shared lowlevel probe names. Additionally dtrace supports putting a "provider" part in the probe names which is essentially a namespacing thing. On systemtap this field is currently ignored (but may be implemented in the future), but this is not really a problem since in systemtap the probes are specified by combining the solib file and the marker name, so there can't really be name conflicts. For the systemtap tapset highlevel probes we instead use names that are systemtapish with single dashes as separators. https://bugzilla.gnome.org/show_bug.cgi?id=606044		2010-05-27 14:51:41 -04:00
..
reference	Initial support for dtrace and systemtap	2010-05-27 14:51:41 -04:00
debugging.txt	Remove references to gruntime. This includes renaming the test program	2002-02-26 21:23:52 +00:00
macros.txt	honour g_mem_gc_friendly settings when freeing slices, make sure	2006-01-25 15:51:43 +00:00
Makefile.am	initialize automake variables EXTRA_DIST and TEST_PROGS for unconditional	2007-11-21 20:09:46 +00:00