Lines Matching refs:thread

10 thread stopped and where:
14    * thread #1, queue = 'com.apple.main-thread', stop reason = breakpoint 1.1
21    (lldb) thread backtrace
22    * thread #1, queue = 'com.apple.main-thread', stop reason = breakpoint 1.1
31    (lldb) settings set thread-stop-format STRING
34 The first of these is an abbreviated thread output, that just contains data
35 about the thread, and not the stop frame. It will always get used in situations
39 There is another thread format used for commands like thread list where the
40 thread information isn't followed by frame info. In that case, it is convenient
41 to have frame zero information in the thread output. That format is set by:
45    (lldb) settings set thread-format STRING
129 | ``thread.id``                                     | The thread identifier for the current thread …
131 | ``thread.index``                                  | The unique one based thread index ID which is…
133 | ``thread.name``                                   | The name of the thread if the target OS suppo…
135 | ``thread.queue``                                  | The queue name of the thread if the target OS…
137 | ``thread.stop-reason``                            | A textual reason why the thread stopped. If t…
139 | ``thread.stop-reason-raw``                        | A textual reason why the thread stopped. Alwa…
141 | ``thread.return-value``                           | The return value of the latest step operation…
143 | ``thread.completed-expression``                   | The expression result for a thread that just …
151 | ``script.thread:python_func``                     | Use a Python function to generate a piece of …
225 values for the frame and thread format strings. These can be accessed with the
230    (lldb) settings show thread-format
231 …thread-format (format-string) = "thread #${thread.index}: tid = ${thread.id%tid}{, ${frame.pc}}{ $…
235 When making thread formats, you will need surround any of the information that
236 comes from a stack frame with scopes ({ frame-content }) as the thread format
238 for a thread, we don't need to duplicate the information for frame zero in the
239 thread information:
243   (lldb) thread backtrace
244   thread #1: tid = 0x2e03, stop reason = breakpoint 1.1 2.1
257 Looking at the default format for the thread, and underlining the frame
262 …thread #${thread.index}: tid = ${thread.id}{, ${frame.pc}}{ ${module.file.basename}`${function.nam…
266 thread information is displayed in a context where we only want to show thread
269 For both thread and frame formats, you can use ${script.target:python_func},
270 ${script.process:python_func} and ${script.thread:python_func} (and of course
287    def thread_printer_func (thread,unused):
288      return "Thread %s has %d frames\n" % (thread.name, thread.num_frames)
294    (lldb) settings set thread-format "${script.thread:thread_printer_func}"