Mercurial > dropbear

comparison debug.h @ 94:c85c88500ea6

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
DEBUG_TRACE now only triggers with -v on the cmdline
author Matt Johnston <matt@ucc.asn.au>
date Wed, 18 Aug 2004 15:48:25 +0000
parents a54d20c96178
children d3eb1fa8484e
comparison
equal deleted inserted replaced
93:5dda5a4d475c 94:c85c88500ea6
31 31
32 /* Work well for valgrind - don't clear environment, be nicer with signals 32 /* Work well for valgrind - don't clear environment, be nicer with signals
33 * etc. Don't use this normally, it might cause problems */ 33 * etc. Don't use this normally, it might cause problems */
34 /* #define DEBUG_VALGRIND */ 34 /* #define DEBUG_VALGRIND */
35 35
36 /* Define this to print trace statements - very verbose */ 36 /* Define this to compile in trace debugging printf()s. You'll need to
37 /* Caution: Don't use this in an unfriendly environment (ie unfirewalled), 37 * run programs with "-v" to turn this on.
38 * since the printing does not sanitise strings etc */ 38 * Caution: Don't use this in an unfriendly environment (ie unfirewalled),
39 * since the printing may not sanitise strings etc. This will add a reasonable
40 * amount to your executable size. */
39 /* #define DEBUG_TRACE */ 41 /* #define DEBUG_TRACE */
40 42
41 /* All functions writing to the cleartext payload buffer call 43 /* All functions writing to the cleartext payload buffer call
42 * CHECKCLEARTOWRITE() before writing. This is only really useful if you're 44 * CHECKCLEARTOWRITE() before writing. This is only really useful if you're
43 * attempting to track down a problem */ 45 * attempting to track down a problem */