Lines Matching refs:to
6 Various classes, functions and macros are provided in wxWidgets to help you debug
9 defined. You can also test the \_\_WXDEBUG\_\_ symbol in your own applications to execute
15 various static functions and variables. It allows you to dump all objects to that stream, write statistics about object allocation, and
18 It is good practice to define a \helpref{wxObject::Dump}{wxobjectdump} member function for each class you derive
26 detect memory leaks when your application is about to exit, and if there are any leaks,
28 and compiler -- some systems don't allow all memory logging to be enabled). See the
31 For wxDebugContext to do its work, the {\it new} and {\it delete}\rtfsp
32 operators for wxObject have been redefined to store extra information
35 find difficult-to-detect memory leaks (objects are not
37 underwrites (writing to memory in front of the object).
40 wxUSE\_DEBUG\_NEW\_ALWAYS are set to 1 in setup.h, 'new' is defined to be:
52 compilers allow this definition to work properly, but most do.
57 scattering wxASSERTs liberally to test for problems in your code as early as possible. Forward thinking
60 \helpref{wxASSERT}{wxassert} is used to pop up an error message box when a condition
61 is not true. You can also use \helpref{wxASSERT\_MSG}{wxassertmsg} to supply your
75 The message box allows you to continue execution or abort the program. If you are running
76 the application inside a debugger, you will be able to see exactly where the problem was.
80 You can use the \helpref{wxLogDebug}{wxlogdebug} and \helpref{wxLogTrace}{wxlogtrace} functions to output debugging information in debug mode;
94 to a file, instead of the default standard error or debugger output);
97 Check to check memory blocks for integrity.
116 at any other time (if wxUSE\_DEBUG\_CONTEXT is set to 1 in setup.h). It is not disabled
117 in non-debug mode because you may not wish to recompile wxWidgets and your entire application
118 just to make use of the error logging facility.