rfc:debugoptions
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
rfc:debugoptions [2011/01/14 21:40] – stas | rfc:debugoptions [2017/09/22 13:28] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 10: | Line 10: | ||
===== Introduction ===== | ===== Introduction ===== | ||
- | Debug backtrace functions are a very useful debug tool. However, for big projects, the problem that often happens is that when something happens inside the code, the debug trace becomes so big it's unmanageable. This is because it includes the arguments, and those can be complex data arrays, huge objects, etc. so when the trace is prepared or printed out, the useful information is drowned in the mass of white noise. | + | Debug backtrace functions are a very useful debug tool. However, for big projects, the problem that often happens is that when something happens inside the code, the debug trace becomes so big it's unmanageable. This is because it always |
===== Proposal ===== | ===== Proposal ===== | ||
Line 17: | Line 17: | ||
^ Constant | ^ Constant | ||
- | ^ DEBUG_BACKTRACE_PROVIDE_OBJECT | + | | DEBUG_BACKTRACE_PROVIDE_OBJECT |
- | ^ DEBUG_BACKTRACE_IGNORE_ARGS | + | | DEBUG_BACKTRACE_IGNORE_ARGS |
The default options will be DEBUG_BACKTRACE_PROVIDE_OBJECT, | The default options will be DEBUG_BACKTRACE_PROVIDE_OBJECT, |
rfc/debugoptions.1295041205.txt.gz · Last modified: 2017/09/22 13:28 (external edit)