/netbsd-src/external/apache2/llvm/dist/llvm/utils/ |
H A D | lldbDataFormatters.py | 9 def __lldb_init_module(debugger, internal_dict): argument 10 debugger.HandleCommand('type category define -e llvm -l c++') 11 debugger.HandleCommand('type synthetic add -w llvm ' 14 debugger.HandleCommand('type synthetic add -w llvm ' 17 debugger.HandleCommand('type synthetic add -w llvm ' 20 debugger.HandleCommand('type synthetic add -w llvm ' 23 debugger.HandleCommand('type summary add -w llvm ' 26 debugger.HandleCommand('type summary add -w llvm ' 29 debugger.HandleCommand('type summary add -w llvm ' 32 debugger.HandleCommand('type summary add -w llvm '
|
/netbsd-src/sys/external/bsd/acpica/conf/ |
H A D | files.acpica | 12 # debugger/ 13 file debugger/dbcmds.c acpica & acpi_debug & ddb 14 file debugger/dbconvert.c acpica & acpi_debug & ddb 15 file debugger/dbdisply.c acpica & acpi_debug & ddb 16 file debugger/dbexec.c acpica & acpi_debug & ddb 17 file debugger/dbhistry.c acpica & acpi_debug & ddb 18 file debugger/dbinput.c acpica & acpi_debug & ddb 19 file debugger/dbmethod.c acpica & acpi_debug & ddb 20 file debugger/dbnames.c acpica & acpi_debug & ddb 21 file debugger/dbobject.c acpica & acpi_debug & ddb [all …]
|
/netbsd-src/external/apache2/llvm/dist/llvm/docs/ |
H A D | Bugpoint.rst | 42 causes the verifier to abort), ``bugpoint`` starts the `crash debugger`_. 48 selected code generator crashes, ``bugpoint`` starts the `crash debugger`_ on 51 failure, and starts the `code generator debugger`_. 57 `miscompilation debugger`_. Otherwise, there is no problem ``bugpoint`` can 60 .. _crash debugger: 62 Crash debugger 81 .. _code generator debugger: argument 83 Code generator debugger 86 The code generator debugger attempts to narrow down the amount of code that is 95 problem. The code generator debugger assumes that the "safe" backend produces [all …]
|
H A D | DebuggingJITedCode.rst | 22 ``__jit_debug_register_code`` that the debugger knows about. When the debugger 25 debugger catches the breakpoint signal, loads the new object file from the
|
H A D | SourceLevelDebugging.rst | 53 When a program is being debugged, a debugger interacts with the user and turns 55 such, a debugger must be aware of the source-language, and is thus tied to a 93 current state of the program with a debugger, such as setting program 112 the program as it executes from a debugger. Compiling a program with 149 Debug information is designed to be agnostic about the target debugger and 154 debugger to interpret the information. 156 To provide basic functionality, the LLVM debugger does have to make some 158 these to a minimum. The only common features that the LLVM debugger assumes 161 debugger to form stack traces, show information about local variables, etc. 347 together to allow a debugger to analyze the relationship between statements, [all …]
|
/netbsd-src/external/apache2/llvm/dist/clang/utils/ |
H A D | ClangDataFormat.py | 24 def __lldb_init_module(debugger, internal_dict): argument 25 …debugger.HandleCommand("type summary add -F ClangDataFormat.SourceLocation_summary clang::SourceLo… 26 debugger.HandleCommand("type summary add -F ClangDataFormat.QualType_summary clang::QualType") 27 debugger.HandleCommand("type summary add -F ClangDataFormat.StringRef_summary llvm::StringRef")
|
H A D | clangdiag.py | 163 def the_diag_command(debugger, command, exe_ctx, result, dict): argument 183 def __lldb_init_module(debugger, dict): argument 190 debugger.HandleCommand(
|
/netbsd-src/sys/arch/hpcsh/conf/ |
H A D | DEBUG | 9 options DDB # in-kernel debugger 10 #options KGDB # remote debugger
|
H A D | HPW650PA | 25 options DDB # in-kernel debugger 27 #options KGDB # in-kernel debugger
|
/netbsd-src/sys/arch/mipsco/stand/common/ |
H A D | start.S | 42 sw zero, CALLFRAME_RA(sp) # clear ra for debugger 43 sw zero, CALLFRAME_SP(sp) # clear fp for debugger
|
/netbsd-src/external/gpl3/gcc.old/dist/gcc/jit/docs/cp/topics/ |
H A D | locations.rst | 27 statements in the JIT-compiled code, allowing the debugger to 37 the debugger: 65 file, giving you *something* you can step through in the debugger.
|
/netbsd-src/external/gpl3/gcc/dist/gcc/jit/docs/cp/topics/ |
H A D | locations.rst | 27 statements in the JIT-compiled code, allowing the debugger to 37 the debugger: 65 file, giving you *something* you can step through in the debugger.
|
/netbsd-src/external/gpl3/gcc/dist/gcc/jit/docs/topics/ |
H A D | locations.rst | 27 statements in the JIT-compiled code, allowing the debugger to 37 the debugger: 73 file, giving you *something* you can step through in the debugger.
|
/netbsd-src/external/gpl3/gcc.old/dist/gcc/jit/docs/topics/ |
H A D | locations.rst | 27 statements in the JIT-compiled code, allowing the debugger to 37 the debugger: 73 file, giving you *something* you can step through in the debugger.
|
/netbsd-src/distrib/syspkg/sets/comp/comp-debug-bin/ |
H A D | DESCR | 14 gdb - is the GNU debugger. The purpose of a debugger such as GDB
|
/netbsd-src/distrib/syspkg/sets/comp/comp-debug-man/ |
H A D | DESCR | 15 gdb - is the GNU debugger. The purpose of a debugger such as GDB
|
/netbsd-src/distrib/syspkg/sets/comp/comp-debug-catman/ |
H A D | DESCR | 15 gdb - is the GNU debugger. The purpose of a debugger such as GDB
|
/netbsd-src/sys/arch/cobalt/stand/boot/ |
H A D | start.S | 42 sw zero, CALLFRAME_RA(sp) # clear ra for debugger 43 sw zero, CALLFRAME_SP(sp) # clear fp for debugger
|
/netbsd-src/sys/arch/pmax/stand/common/ |
H A D | start.S | 96 sw zero, CALLFRAME_RA(sp) # Zero out old ra for debugger 97 sw zero, CALLFRAME_SP(sp) # Zero out old fp for debugger
|
/netbsd-src/external/apache2/llvm/dist/llvm/bindings/python/ |
H A D | README.txt | 31 To step into the Python debugger while running a test, add the following 32 to your test at the point you wish to enter the debugger:
|
/netbsd-src/external/gpl3/binutils/dist/gas/doc/ |
H A D | c-score.texi | 127 function's stack frame, this is for the debugger to explain the 132 when you want to generate information for the debugger. 136 for the debugger.
|
/netbsd-src/external/gpl3/binutils.old/dist/gas/doc/ |
H A D | c-score.texi | 127 function's stack frame, this is for the debugger to explain the 132 when you want to generate information for the debugger. 136 for the debugger.
|
/netbsd-src/sys/external/bsd/acpica/dist/generate/lint/ |
H A D | files.lnt | 4 ..\..\source\components\debugger\*.c
|
/netbsd-src/external/mit/xorg/bin/xedit/lisp/ |
H A D | Makefile | 8 SRCS= bytecode.c core.c debugger.c format.c hash.c helper.c \
|
/netbsd-src/sys/arch/hpcmips/conf/ |
H A D | LROUTER | 25 options DDB # in-kernel debugger 27 #options DDB_ONPANIC=0 # don't enter debugger on panic 28 #options KGDB # remote debugger
|