Lines Matching +full:lldb +full:- +full:build

5 ---------------------------------------------
8 information. Typically this means passing -g to the compiler when compiling
12 etc), LLDB by default will only search for compile units whose filename
24 "foo.c". If your code does this, or if your build system combines multiple
26 compiled into another implementation file, you will need to tell LLDB to always
32    $ echo "settings set target.inline-breakpoint-strategy always" >> ~/.lldbinit
34 This tells LLDB to always look in all compile units and search for breakpoint
49 If you are using an IDE and you move your project in your file system and build
50 again, sometimes doing a clean then build will solve the issue.This will fix
52 the build folder might still contain stale debug information with the old
56 ---------------------------------------
63    (lldb) file /tmp/a.out
64    (lldb) image list
65    [  0] 71E5A649-8FEF-3887-9CED-D3EF8FC2FD6E 0x0000000100000000 /tmp/a.out
67    [  1] 6900F2BA-DB48-3B78-B668-58FC0CF6BCB8 0x00007fff5fc00000 /usr/lib/dyld
69    (lldb) script lldb.target.module['/tmp/a.out'].GetNumCompileUnits()
71    (lldb) script lldb.target.module['/usr/lib/dyld'].GetNumCompileUnits()
81    (lldb) script
82    Python Interactive Interpreter. To exit, type 'quit()', 'exit()' or Ctrl-D.
83    >>> m = lldb.target.module['a.out']
93 in the debug info and this can cause LLDB to not resolve breakpoints. You can
94 use the breakpoint list command with the --verbose option to see the full paths
99    (lldb) breakpoint list --verbose