Searched refs:debug (Results 1 – 18 of 18) sorted by relevance
232 self.log.debug(286 self.log.debug("Found:")289 self.log.debug(" {:4} Total {} Macros"291 self.log.debug(" {:4} {} Non-identifier Macros"293 self.log.debug(" {:4} Enum Constants".format(len(enum_consts)))294 self.log.debug(" {:4} Identifiers".format(len(identifiers)))295 self.log.debug(" {:4} Exported Symbols".format(len(symbols)))383 self.log.debug("Looking for macros in {} files".format(len(files)))418 self.log.debug(451 self.log.debug("Looking for enum consts in {} files".format(len(files)))[all …]
465 logger.debug("Done!")
163 self.log.debug(174 self.log.debug(fetch_output.decode("utf-8"))177 self.log.debug("Checking out git worktree for revision {}".format(187 self.log.debug(worktree_output.decode("utf-8"))193 self.log.debug("Commit is {}".format(version.commit))205 self.log.debug(update_output.decode("utf-8"))217 self.log.debug(fetch_output.decode("utf-8"))227 self.log.debug(checkout_output.decode("utf-8"))242 self.log.debug(make_output.decode("utf-8"))276 self.log.debug(abi_dump_output.decode("utf-8"))[all …]
310 self.logger.debug("Using current work directory.")313 self.logger.debug("Creating git worktree for {}."338 self.logger.debug("Building library/*.o for {}."368 self.logger.debug("Measuring code size for {} by `{}`."388 self.logger.debug("Removing temporary worktree {}."797 self.logger.debug("Code size csv file for {} already exists."805 self.logger.debug("Generating code size csv for {}."836 self.logger.debug("Generating comparison results between {} and {}."
107 char debug = 0; /* flag for debug messages */ variable143 if (debug) { in printf_dbg()190 debug = 1; in parse_arguments()983 if (debug) { in main()
21 However, when it comes to TLS, we also have the option of using debug messages26 good to have a debug message checked by the test case to confirm that the
109 …ibraries in addition to the static libraries. Setting `DEBUG` gives you a debug build. You can ove…144 - `Debug`. This generates debug information and disables optimization of the code.145 - `Coverage`. This generates code coverage information in addition to debug information.147 - `ASanDbg`. Same as ASan but slower, with debug information and better stack traces.149 - `MemSanDbg`. Same as MemSan but slower, with debug information, better stack traces and origin …152 Switching build modes in CMake is simple. For debug mode, enter at the command line:
74 # VScode folder to store local debug files and configurations
257 set(CMAKE_C_FLAGS_DEBUG "--debug -On")
696 * Fix very high stack usage in SSL debug code. Reported by Maximilian2034 could notably be triggered by setting the TLS debug level to 3 or above2361 * Add missing arguments of debug message in mbedtls_ssl_decrypt_buf.2662 * Fix a function name in a debug message. Contributed by Ercan Ozturk in3596 algorithms section is too short. In builds with debug output, the overread3597 data is output with the debug data.4270 * Fixed cert_app.c sample program for debug output and for use when no root4550 * Prepend a "thread identifier" to debug messages (issue pointed out by4611 * The SSL debug callback gained two new arguments (file name, line number).4865 * Added new error codes and debug messages about selection of[all …]
35 #include "mbedtls/debug.h"
40 /* Detect if debug messages output partial lines and mark them */
721 /* unsupported functions: check_pair, debug */
4 #include <mbedtls/debug.h>
6056 # Test case manually extracted from debug output of TLS-PSK run
188 debug.o \
110 debug.c
124 | `debug.h` | `mbedtls_debug_` | No change (not a crypto API) |1070 There is no PSA equivalent of the debug functionality provided by `mbedtls_pk_debug`. Use `psa_expo…
