Home
last modified time | relevance | path

Searched refs:debugging (Results 1 – 25 of 930) sorted by relevance

12345678910>>...38

/third_party/abseil-cpp/
DBUILD.gn98 "${ABSEIL_DIR}/absl/debugging/internal/address_is_readable.cc",
99 "${ABSEIL_DIR}/absl/debugging/internal/address_is_readable.h",
100 "${ABSEIL_DIR}/absl/debugging/internal/elf_mem_image.cc",
101 "${ABSEIL_DIR}/absl/debugging/internal/stacktrace_aarch64-inl.inc",
102 "${ABSEIL_DIR}/absl/debugging/internal/stacktrace_arm-inl.inc",
103 "${ABSEIL_DIR}/absl/debugging/internal/stacktrace_config.h",
104 "${ABSEIL_DIR}/absl/debugging/internal/stacktrace_generic-inl.inc",
105 "${ABSEIL_DIR}/absl/debugging/internal/stacktrace_powerpc-inl.inc",
106 "${ABSEIL_DIR}/absl/debugging/internal/stacktrace_unimplemented-inl.inc",
107 "${ABSEIL_DIR}/absl/debugging/internal/stacktrace_win32-inl.inc",
[all …]
/third_party/skia/third_party/externals/abseil-cpp/CMake/
DAbseilDll.cmake95 "debugging/failure_signal_handler.cc"
96 "debugging/failure_signal_handler.h"
97 "debugging/leak_check.h"
98 "debugging/leak_check_disable.cc"
99 "debugging/stacktrace.cc"
100 "debugging/stacktrace.h"
101 "debugging/symbolize.cc"
102 "debugging/symbolize.h"
103 "debugging/internal/address_is_readable.cc"
104 "debugging/internal/address_is_readable.h"
[all …]
/third_party/flutter/skia/third_party/externals/freetype/docs/
DDEBUG7 There are several ways to enable debugging features in a FreeType 2
25 The trace macros are used to send debugging messages when an
32 small but effective debugging memory manager that tracks all
41 debugging memory manager never frees the blocks to the heap in
44 When FT2_DEBUG_MEMORY isn't defined at runtime, the debugging
52 debugging its code:
82 The FT_TRACE macro is used to send general-purpose debugging
127 The following environment variables control debugging output and
157 debugging memory manager that will track leaking memory blocks as
160 considerably saves time when debugging new additions to the
[all …]
/third_party/python/Lib/
Dftplib.py98 debugging = 0 variable in FTP
168 if self.debugging:
178 self.debugging = level
200 if self.debugging > 1:
206 if self.debugging: print('*cmd*', self.sanitize(line))
215 if self.debugging > 1:
245 if self.debugging:
270 if self.debugging > 1:
468 if self.debugging > 2:
938 debugging = 0
[all …]
Dpipes.py87 self.debugging = 0
103 t.debugging = self.debugging
108 self.debugging = flag
175 if self.debugging:
/third_party/skia/third_party/externals/abseil-cpp/patches/
D0003-delete-static-initializer-in-stacktrace.patch1 …git a/third_party/abseil-cpp/absl/debugging/internal/stacktrace_generic-inl.inc b/third_party/abse…
3 --- a/third_party/abseil-cpp/absl/debugging/internal/stacktrace_generic-inl.inc
4 +++ b/third_party/abseil-cpp/absl/debugging/internal/stacktrace_generic-inl.inc
/third_party/typescript/scripts/
DbrowserIntegrationTest.js18 const debugging = false; constant
22 const browser = await playwright[browserType].launch({ headless: !debugging });
41 if (!debugging) {
/third_party/openssl/
DNOTES-VMS.md8 - [About debugging](#about-debugging)
61 About debugging
64 If you build for debugging, the default on VMS is that image
69 Generally speaking, if you build for debugging, only use the programs
70 directly for debugging. Do not try to use them from a script, such
81 Then just run it and you will find yourself in a debugging session.
/third_party/freetype/docs/
DDEBUG7 There are several ways to enable debugging features in a FreeType 2
25 The trace macros are used to send debugging messages when an
32 small but effective debugging memory manager that tracks all
41 memory (the debugging memory manager never frees the blocks to the
44 When `FT2_DEBUG_MEMORY' isn't defined at runtime, the debugging
53 debugging messages to a file. The location of the log file has to
67 debugging its code:
97 The `FT_TRACE' macro is used to send general-purpose debugging
142 The following environment variables control debugging output and
209 debugging memory manager that tracks leaking memory blocks as well
[all …]
/third_party/skia/third_party/externals/freetype/docs/
DDEBUG7 There are several ways to enable debugging features in a FreeType 2
25 The trace macros are used to send debugging messages when an
32 small but effective debugging memory manager that tracks all
41 memory (the debugging memory manager never frees the blocks to the
44 When `FT2_DEBUG_MEMORY' isn't defined at runtime, the debugging
53 debugging messages to a file. The location of the log file has to
67 debugging its code:
97 The `FT_TRACE' macro is used to send general-purpose debugging
142 The following environment variables control debugging output and
209 debugging memory manager that tracks leaking memory blocks as well
[all …]
/third_party/flutter/flutter/examples/stocks/lib/
Dstock_settings.dart150 title: const Text('Show material grid (for debugging)'),
159 title: const Text('Show construction lines (for debugging)'),
168 title: const Text('Show baselines (for debugging)'),
177 title: const Text('Show layer boundaries (for debugging)'),
186 title: const Text('Show pointer hit-testing (for debugging)'),
195 title: const Text('Show repaint rainbow (for debugging)'),
/third_party/vk-gl-cts/external/vulkan-docs/src/chapters/
DVK_EXT_debug_marker.adoc5 // This section is included inside the Debugging chapter (debugging.adoc)
8 [[debugging-debug-markers]]
11 Debug markers provide a flexible way for debugging and validation layers to
14 The <<debugging-object-annotation,Object Annotation>> section describes how
17 The <<debugging-command-buffer-markers,Command Buffer Markers>> section
22 [[debugging-object-annotation]]
78 In addition to setting a name for an object, debugging and validation layers
81 For example, a sname:VkShaderModule could have additional debugging data
113 This can be used by debugging layers to easily filter for only data that can
132 [[debugging-command-buffer-markers]]
DVK_EXT_debug_marker.txt5 // This section is included inside the Debugging chapter (debugging.txt)
7 [[debugging-debug-markers]]
10 Debug markers provide a flexible way for debugging and validation layers to
13 The <<debugging-object-annotation,Object Annotation>> section describes how
16 The <<debugging-command-buffer-markers,Command Buffer Markers>> section
21 [[debugging-object-annotation]]
77 In addition to setting a name for an object, debugging and validation layers
80 For example, a sname:VkShaderModule could have additional debugging data
112 This can be used by debugging layers to easily filter for only data that can
131 [[debugging-command-buffer-markers]]
Ddebugging.txt20 [[debugging-object-types]]
118 [[debugging-tooling-info]]
123 Information about tools providing debugging, profiling, or similar services,
214 <<debugging-debug-markers,debug markers>>
220 <<debugging-object-debug-annotation,object debug annotation>>,
221 <<debugging-queue-labels, queue labels>>, or
222 <<debugging-command-buffer-labels, command buffer labels>>
DVK_EXT_debug_utils.txt5 [[debugging-debug-utils]]
8 Vulkan provides flexible debugging utilities for debugging an application.
10 The <<debugging-object-debug-annotation,Object Debug Annotation>> section
14 The <<debugging-queue-labels,Queue Labels>> section describes how to
17 The <<debugging-command-buffer-labels,Command Buffer Labels>> section
21 The <<debugging-debug-messengers,Debug Messengers>> section describes how to
26 [[debugging-object-debug-annotation]]
35 [[debugging-object-naming]]
89 <<debugging-object-types, `VkObjectType` and Vulkan Handle
97 [[debugging-object-data-association]]
[all …]
/third_party/mesa3d/src/gallium/auxiliary/driver_rbug/
DREADME7 It provides remote debugging functionality.
16 which should open gallium remote debugging session. While the program is running
17 you can launch the small remote debugging application from progs/rbug. More
/third_party/node/test/sequential/
Dtest-util-debug.js78 const debugging = `${regexp[0]}/debugging/${regexp[1]}`;
80 `${start}: this { is: ${str[0]}'a'${str[1]} } ${debugging}\n` +
124 debug('this', { is: 'a' }, /debugging/);
/third_party/node/doc/api/
Ddebugger.md9 Node.js includes a command-line debugging utility. To use it, start Node.js
103 It is possible to watch expression and variable values while debugging. On
208 * `repl`: Open debugger's repl for evaluation in debugging script's context
209 * `exec expr`: Execute an expression in debugging script's context
227 instances for debugging and profiling. It uses the
245 debugging sessions.)
250 Chrome DevTools doesn't support debugging [worker threads][] yet.
/third_party/python/Lib/idlelib/
Drpc.py132 def __init__(self, sock, objtable=None, debugging=None): argument
134 if debugging is not None:
135 self.debugging = debugging
154 if not self.debugging:
508 debugging = False variable in RPCHandler
526 debugging = False variable in RPCClient
538 if self.debugging:
/third_party/libinput/doc/user/
Dtroubleshooting.rst14 touchpad-pressure-debugging.rst
16 tablet-debugging.rst
/third_party/python/Lib/test/
Dtest_pipes.py103 self.assertEqual(t.debugging, False)
105 self.assertEqual(t.debugging, True)
200 self.assertEqual(t.debugging, u.debugging)
/third_party/skia/site/docs/dev/tools/
Ddebugvis.md16 …Code](https://skia.googlesource.com/skia/+/refs/heads/main/platform_tools/debugging/vs/Skia.natvis)
17 - [LLDB and Xcode](https://skia.googlesource.com/skia/+/refs/heads/main/platform_tools/debugging/…
/third_party/mesa3d/docs/
Ddebugging.rst7 with debugging. If ``MESA_DEBUG`` is defined, a message will be printed
16 There is a display list printing/debugging facility. See the end of
/third_party/skia/third_party/externals/oboe/samples/MegaDrone/src/main/cpp/
DCMakeLists.txt26 # Enable optimization flags: if having problems with source level debugging,
27 # disable -Ofast ( and debug ), re-enable it after done debugging.
/third_party/skia/third_party/externals/freetype/builds/amiga/
DREADME37 except of the init code, debugging code, and the system interface
53 debugging code which uses vprintf() and exit() (not pure).
58 debugging code which uses KVPrintf() from lib:debug.lib and no
59 exit(). For debugging of Amiga run-time shared system libraries.
85 - Link with either ftsystem.o or ftsystempure.o, if debugging enabled

12345678910>>...38