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

6 LLDB can collect traces and dump them using its symbolication stack.
8 https://easyperf.net/blog/2019/08/23/Intel-Processor-Trace.
11 -------------
26 Build Instructions
27 ------------------
29 Clone and build the low level Intel PT
34   $ mkdir libipt-build
35   $ cmake -S libipt -B libipt-build
36   $ cd libipt-build
39 This will generate a few files in the ``<libipt-build>/lib``
40 and ``<libipt-build>/libipt/include`` directories.
42 Configure and build LLDB with Intel PT support
47       -DLLDB_BUILD_INTEL_PT=ON \
48       -DLIBIPT_INCLUDE_PATH="<libipt-build>/libipt/include" \
49       -DLIBIPT_LIBRARY_PATH="<libipt-build>/lib" \
54   $ cd <lldb-build> && ninja lldb lldb-server # if using Ninja
58 ----------
60 When you are debugging a process, you can turn on intel-pt tracing,
69   lldb <target>
81       [4962256] 0x00007fffeb64c641    movq   %rdi, -0x18(%rbp)
95 --------------------------
99 By default, LLDB uses a buffer of 4KB per thread,
105   thread trace start all -s <size_in_bytes>
110 --------------------------
116   thread trace dump instructions -c <count>
119 -------------------------------------------
133 --------------
151    -> 8       cout << 12 / x << endl;
154     (lldb) thread trace dump instructions -c 5
160         [8385] 0x00000000004009e8    movl   -0x4(%rbp), %ecx
170 ----------------------
173 and decode + symbolicate the trace using LLDB.
182     "type": "intel-pt",
192         "triple": "x86_64-*-linux",
196             "iptTrace": "trace.file" # raw thread-specific trace from the AUX buffer
223   trace schema intel-pt
236   lldb
243 ----------
245 - Original RFC document_ for this feature.
246 - Some details about how Meta is using Intel Processor Trace can be found in this blog_ post.
249 .. _blog: https://engineering.fb.com/2021/04/27/developer-tools/reverse-debugging/