| /minix3/external/bsd/llvm/dist/llvm/utils/ |
| H A D | lldbDataFormatters.py | 7 def __lldb_init_module(debugger, internal_dict): argument 8 debugger.HandleCommand('type category define -e llvm -l c++') 9 debugger.HandleCommand('type synthetic add -w llvm ' 12 debugger.HandleCommand('type synthetic add -w llvm ' 15 debugger.HandleCommand('type synthetic add -w llvm '
|
| /minix3/external/bsd/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 | 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 67 information used by the gdb debugger. Other targets could use the same 89 ability to modify the current state of the program with a debugger, such 110 the program as it executes from a debugger. Compiling a program with 146 Debug information is designed to be agnostic about the target debugger and 151 debugger to interpret the information. 153 To provide basic functionality, the LLVM debugger does have to make some 155 these to a minimum. The only common features that the LLVM debugger assumes 157 <format_global_variables>`. These abstract objects are used by a debugger to [all …]
|
| H A D | MCJITDesignAndImplementation.rst | 174 functions, such as registering the EH frame information with a debugger.
|
| H A D | TestingGuide.rst | 82 These tests are compiled and run under a debugger. The debugger output
|
| H A D | index.rst | 268 source-level debugger.
|
| /minix3/external/bsd/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")
|
| /minix3/external/bsd/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:
|
| /minix3/external/mit/xorg/bin/xedit/lisp/ |
| H A D | Makefile | 8 SRCS= bytecode.c core.c debugger.c format.c hash.c helper.c \
|
| /minix3/external/bsd/llvm/dist/clang/include/clang/Basic/ |
| H A D | LangOptions.def | 171 BENIGN_LANGOPT(DebuggerSupport , 1, 0, "debugger support") 172 BENIGN_LANGOPT(DebuggerCastResultToId, 1, 0, "for 'po' in the debugger, cast the result to id if it… 173 BENIGN_LANGOPT(DebuggerObjCLiteral , 1, 0, "debugger Objective-C literals and subscripting support")
|
| /minix3/external/bsd/llvm/dist/clang/test/CodeGenObjC/ |
| H A D | objc-fixed-enum.m | 4 // so the debugger knows about the signedness of the underlying type.
|
| /minix3/external/bsd/llvm/dist/llvm/docs/tutorial/ |
| H A D | LangImpl8.rst | 17 Source level debugging uses formatted data that helps a debugger 215 constant for C. This is because a debugger wouldn't necessarily understand 219 debugger and have them execute. Secondly, you'll see the "fib.ks" in the 418 generating line information for the function prologue so that the debugger 425 // location in a function are considered part of the prologue and the debugger
|
| H A D | OCamlLangImpl8.rst | 71 - **debugger support** - LLVM supports generation of `DWARF Debug
|
| /minix3/external/bsd/libarchive/dist/libarchive/test/ |
| H A D | README | 51 a memory debugger to try to locate memory leaks in the library;
|
| /minix3/external/bsd/llvm/dist/llvm/docs/CommandGuide/ |
| H A D | llvm-nm.rst | 79 Show all symbols, even debugger only.
|
| /minix3/external/bsd/llvm/dist/llvm/test/DebugInfo/ |
| H A D | debug-info-always-inline.ll | 41 ; call site's line number, setting a breakpoint at the function in the debugger
|
| /minix3/crypto/external/bsd/openssl/dist/test/ |
| H A D | maketests.com | 20 $! Specify DEBUG or NODEBUG P1 to compile with or without debugger
|
| /minix3/crypto/external/bsd/openssl/dist/crypto/ |
| H A D | crypto-lib.com | 25 $! Specify DEBUG or NODEBUG as P2 to compile with or without debugger
|
| /minix3/external/bsd/dhcp/dist/doc/devel/ |
| H A D | atf.dox | 85 approach is convenient for running the test under the debugger.
|
| /minix3/distrib/sets/ |
| H A D | descrs | 339 comp-debug-bin gdb - is the GNU debugger. The purpose of a debugger such as GDB 359 comp-debug-catman gdb - is the GNU debugger. The purpose of a debugger such as GDB 380 comp-debug-man gdb - is the GNU debugger. The purpose of a debugger such as GDB
|
| /minix3/crypto/external/bsd/openssl/dist/ |
| H A D | PROBLEMS | 100 as no debugger support possible at +O3 and additional fprintf()'s
|
| /minix3/external/bsd/llvm/dist/llvm/lib/Support/Windows/ |
| H A D | Signals.inc | 443 // Allow dialog box to pop up allowing choice to start debugger.
|
| /minix3/external/bsd/llvm/dist/clang/include/clang/Driver/ |
| H A D | CC1Options.td | 507 HelpText<"Enable special debugger support behavior">; 511 HelpText<"Enable special debugger support for Objective-C subscripting and literals">;
|
| /minix3/crypto/external/bsd/openssl/dist/ssl/ |
| H A D | ssl-lib.com | 24 $! Specify DEBUG or NODEBUG as P2 to compile with or without debugger
|
| /minix3/external/public-domain/xz/dist/ |
| H A D | README | 174 $ gdb /path/to/app-binary # Load the app to the debugger.
|