haiku/build/config_headers
Ingo Weinhold e1c6140eaa mmlr + bonefish:
* Add optional stack trace capturing for slab memory manager tracing.
* Add allocation tracking for the slab allocator (enabled via
  SLAB_ALLOCATION_TRACKING). The allocation tracking requires tracing
  with stack traces to be enabled for object caches and/or the memory
  manager.
  - Add class AllocationTrackingInfo that associates an allocation with
    its respective tracing entry. The structure is added to the end of
    an allocation done by the memory manager. For the object caches
    there's a separate array for each slab.
  - Add code range markers to the slab code, so that the first caller
    into the slab code can be retrieved from the stack traces.
  - Add KDL command "allocations_per_caller" that lists all allocations
    summarized by caller.
* Move debug definitions from slab_private.h to slab_debug.h.


git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@43072 a95241bf-73f2-0310-859d-f6bbb57e9c96
2011-11-01 18:34:21 +00:00
..
apps_debugger_config.h * More work on retrieving local variable values. Address and compound types can 2009-09-21 04:39:40 +00:00
kernel_debug_config.h mmlr + bonefish: 2011-11-01 18:34:21 +00:00
kernel_debugger_config.h * Forgot to put us keymap as the default one 2008-06-20 23:29:56 +00:00
paranoia_config.h * Paranoia checks were accidentally globally enabled by default. Object 2008-04-27 15:13:31 +00:00
ReadMe Added a small ReadMe about custom build headers. 2008-10-23 09:18:05 +00:00
support_kit_config.h Added support_kit_config.h configuration header. ATM it only contains a 2008-04-22 15:04:01 +00:00
tracing_config.h mmlr + bonefish: 2011-11-01 18:34:21 +00:00

To customize the settings defined in these headers, create a folder "user_config_headers" in the "build" folder and copy the headers you want to modify into that folder. Your custom headers will be ignored by SVN and the build system will automatically use them instead of the original ones. But be aware that when changes are commited to the files in "config_headers", you will have to apply them to your custom headers manually.