lldb

问题 After upgrading to Xcode 10.0 the debugger is failing to perform basic functions. It's possible the debugger problems are unrelated to the upgrade to 10.0 but I suspect this as the catalyst. Symptoms: Breakpoints are breaking properly The "local variables" area (not sure if this is the proper term) lists local variables but cannot provide any info on them. Attempting something like "Print description of x" The result is an error message: Printing description of x x = <could not resolve type>

问题 I have searched for topics specifically to this question but have not found anything close to my experience. Forgive me if I have overlooked the answer. I am familiar with GDB and exception points, break points, etc... but the following test of debugging in GDB vs LDB left me without a plausible response. Global Test Values Xcode 4.2.1 New Single Window Project (Default template w/no changes) Arc Enabled Storyboard Enabled Case 1 - GDB Debugger Exception Breakpoint Values: Exception - All

问题 this is my first experience in commandline mode of lldb. unsuccessful. installed minimal kit with clang, lld, lldb v5 (ubuntu 16.04) sample application built with clang. trying to start: lldb applcation >run error: process launch failed: unable to locate lldb-server-5.0.0 so now the questions: why lldb tries to run a server? this is not a remote debugging. why lldb refers to 5.0.0 (and where to change this setting)? actually there was added symbolic links automiticaly with xxx-5.0 suffix to

问题 Similar to this question: How can I avoid debugging into Boost source code in Visual Studio? But how can I do it in Xcode? Thanks, Jim 回答1: The key is the lldb setting target.process.thread.step-avoid-regexp . On my Mac, this had the default value ^std:: . You might want to check it on your setup by entering lldb and typing settings show target.process.thread.step-avoid-regexp . Anyway, what you can do is edit ~/.lldbinit, creating it if it does not yet exist, and add a line like settings set

问题 I've set a breakpoint with the condition... [event.name isEqualToString:@"Some Name"] This works fine. However, when I try to add another breakpoint with the condition... [part.name isEqualToString:@"Some Value With A Pound Sign £"] I get the error... Internal error [IRForTarget]: An Objective-C constant string's string initializer is not an array Stopped due to an error evaluating condition of breakpoint Do I need to escape the pound sign or something? 回答1: There's a bug with the expression

问题 I am reading the Dancing in the Debugger — A Waltz with LLDB article. And I am trying the thread return command with Swift 2.2 as well as Swift 3.0. My code is pretty simple: class ViewController: UIViewController { override func viewDidLoad() { super.viewDidLoad() let resust = test() print(resust) } func test() -> Bool { return true } } and I added a breakpoint at the beginning of the test() function with a thread return false action. However, after command+R, my program stops at the

问题 I am trying to debug an EXC_BAD_ACCESS in my iPhone app. It is crashing on a method call and on the line of the method is EXC_BAD_ACCESS (code=1, address = xxx) . Before, I would have just used gdb info malloc-history <xxx> to start debugging, but I am having trouble finding a parallel command in LLDB . I saw this thread that said to use Instruments, but when I do I still get the crash but I can't figure out how to tell exactly where the app is crashing from in Instruments. I just need to

问题 I'm using Swift 3, Xcode 8.1, CocoaPods 1.1.1. After running pod update , every time i try to use Xcode's lldb console - it prints an error. For example, po self outputs: Shared Swift state for My App has developed fatal errors and is being discarded. REPL definitions and persistent names/types will be lost. warning: Swift error in module My App . Debug info from this module will be unavailable in the debugger. error: in auto-import: failed to get module ' My_App ' from AST context: Does

问题 Recently (I suspect some system/homebrew update) the Qt's debugger stopped working. It hangs forever on Setting up inferior... The internal log: dStart parameters: 'QGIS' mode: 1 dABI: x86-darwin-generic-mach_o-64bit dLanguages: c++ dExecutable: ./QGIS dDirectory: ./build/output/bin/QGIS.app/Contents/MacOS dDebugger: /Library/Developer/CommandLineTools/usr/bin/lldb dProject: ./QGIS dAdditional Search Directories: dSysroot: dDebug Source Location: dDebugger settings: dAdditionalArguments: