| /llvm-project-15.0.7/lldb/source/Plugins/Trace/intel-pt/ |
| H A D | TraceIntelPTJSONStructs.cpp | 101 {"stepping", cpu_info.stepping}, in toJSON() 108 uint64_t family, model, stepping; in fromJSON() local 110 o.map("model", model) && o.map("stepping", stepping))) in fromJSON() 115 cpu_info.stepping = stepping; in fromJSON()
|
| H A D | TraceIntelPT.cpp | 442 int64_t stepping = -1; in GetCPUInfoForLiveProcess() local 466 columns[1].getAsInteger(10, stepping)) in GetCPUInfoForLiveProcess() 475 if ((cpu_family != -1) && (model != -1) && (stepping != -1) && in GetCPUInfoForLiveProcess() 480 static_cast<uint8_t>(stepping)}; in GetCPUInfoForLiveProcess()
|
| H A D | TraceIntelPTBundleLoader.cpp | 163 "stepping": integer in GetSchema()
|
| /llvm-project-15.0.7/lldb/test/API/lang/objc/direct-dispatch-step/ |
| H A D | Makefile | 1 OBJC_SOURCES := stepping-tests.m
|
| H A D | stepping-tests.m | 93 obj = [OverridesALot alloc]; // Stop here to start stepping
|
| /llvm-project-15.0.7/lldb/test/API/lang/objc/objc-stepping/ |
| H A D | Makefile | 1 OBJC_SOURCES := stepping-tests.m
|
| H A D | stepping-tests.m | 130 // We also had a bug where stepping into a method dispatch to nil turned
|
| /llvm-project-15.0.7/cross-project-tests/debuginfo-tests/dexter/dex/debugger/dbgeng/ |
| H A D | README.md | 24 have to use the DbgEng stepping interface, or we would effectively be 26 stepping) only seem to be possible from the command interface.
|
| /llvm-project-15.0.7/openmp/runtime/src/ |
| H A D | kmp_utility.cpp | 160 p->stepping = get_value(buf.eax, 0, 0x0f); in __kmp_query_cpuid() 165 p->family, p->model, p->stepping)); in __kmp_query_cpuid()
|
| /llvm-project-15.0.7/lldb/source/Target/ |
| H A D | TargetProperties.td | 145 def UseFastStepping: Property<"use-fast-stepping", "Boolean">, 147 …Desc<"Use a fast stepping algorithm based on running from branch to branch rather than instruction… 226 …Desc<"If true, warn when stopped in code that is optimized where stepping and variable availabilit… 242 …Desc<"If true, stepping operations will run all threads. This is equivalent to setting the run-mo… 279 Desc<"A list of libraries that source stepping won't stop in.">;
|
| /llvm-project-15.0.7/llvm/test/CodeGen/X86/ |
| H A D | load-combine-dbg.ll | 2 ; This was extracted from a swift debugger stepping testcase and checks that the
|
| /llvm-project-15.0.7/llvm/test/DebugInfo/Generic/ |
| H A D | pr40628.ll | 8 ; variable after stepping onto the return instruction.
|
| /llvm-project-15.0.7/lldb/test/Shell/ExecControl/StopHook/ |
| H A D | stop-hook.test | 55 # CHECK: ->{{.*}} // We should stop here after stepping.
|
| /llvm-project-15.0.7/llvm/test/DebugInfo/Mips/ |
| H A D | fn-call-line.ll | 18 ; which would cause confusing stepping behaviour for the end user.
|
| /llvm-project-15.0.7/llvm/docs/ |
| H A D | HowToUpdateDebugInfo.rst | 42 source locations, even though this may lead to jumpy single-stepping 85 single-stepping (or breakpoint) behavior. Often, merged instructions are memory 115 single-stepping experience. The rule for 133 The purpose of this rule is to prevent erratic or misleading single-stepping
|
| /llvm-project-15.0.7/lldb/test/API/tools/lldb-server/ |
| H A D | main.cpp | 132 #warning This may generate unpredictible assembly and cause the single-stepping test to fail. in swap_chars()
|
| /llvm-project-15.0.7/lldb/docs/status/ |
| H A D | projects.rst | 90 and other things like the scripted stepping operations and any fancier 180 that makes stepping less efficient, since now you have to fetch the thread list 181 on every step or stepping doesn't work correctly. This is especially an issue 260 implement stepping, this savings could be significant on slow connections. 391 point if you know the exception will unwind past the frame you were stepping in,
|
| /llvm-project-15.0.7/lldb/tools/debugserver/source/ |
| H A D | ChangeLog | 199 Merged Yusuf's changes to make software single stepping work. 221 single stepping through Thumb IT blocks. 225 properly handles Thumb IT software single stepping. 249 single stepping. 289 will log and exit when we are verifying software single stepping (a 296 software single stepping. 593 (DNBArchMachARM::EnableHardwareSingleStep): Handle hardware single stepping 597 if single stepping wasn't able to complete in a single run. 599 if stepping is not complete. 857 * FunctionProfiler.cpp: New class that allows single stepping through [all …]
|
| /llvm-project-15.0.7/llvm/test/DebugInfo/MIR/X86/ |
| H A D | mlicm-hoist-pre-regalloc.mir | 4 ; Doing so causes poor stepping bevavior.
|
| /llvm-project-15.0.7/cross-project-tests/debuginfo-tests/dexter/ |
| H A D | Commands.md | 76 Expect to see a particular step `kind` a number of `times` while stepping 207 Define a limited stepping range that may be predicated on a condition. When the
|
| /llvm-project-15.0.7/lldb/docs/use/ |
| H A D | python-reference.rst | 426 Using the python API' to create custom stepping logic 429 A slightly esoteric use of the Python API's is to construct custom stepping 430 types. LLDB's stepping is driven by a stack of "thread plans" and a fairly 460 | | | stepping in a particular stack frame, bu… 470 … | Also, do any work you need here to set up the next stage of stepping. | 482 used to compose more complex stepping operations. When you use subsidiary plans
|
| H A D | intel_pt.rst | 190 "stepping": 1
|
| H A D | tutorial.rst | 476 … this will be particularly important. For convenience, however, all the stepping commands have eas… 478 The other program stepping commands are pretty much the same as in gdb. You've got: 496 Finally, lldb has a run until line or frame exit stepping mode:
|
| /llvm-project-15.0.7/lldb/source/Commands/ |
| H A D | Options.td | 1041 Desc<"A boolean value that sets whether stepping into functions will step " 1045 Desc<"A boolean value, if true stepping out of functions will continue to" 1048 Desc<"How many times to perform the stepping operation - currently only " 1051 Group<1>, Arg<"LineNum">, Desc<"The line at which to stop stepping - " 1058 "threads while stepping the current thread.">; 1061 "function names to not to stop at when stepping in.">; 1064 "function step in should stop at when stepping into.">; 1074 "threads while stepping this one">;
|
| /llvm-project-15.0.7/lldb/docs/ |
| H A D | lldb-for-gdb-users.txt | 259 convenience, however, all the stepping commands have easy aliases. 262 The other program stepping commands are pretty much the same as in gdb.
|