[Lldb-commits] [PATCH] D33426: Introduce new command: thread backtrace unique
Brian Gianforcaro via Phabricator via lldb-commits
lldb-commits at lists.llvm.org
Fri May 26 23:16:41 PDT 2017
bgianfo updated this revision to Diff 100529.
bgianfo marked 7 inline comments as done.
bgianfo added a comment.
Address Pavel and Greg's feedback on Diff 100365.
Pavel: I took your suggestions to make the test case more readable,
I really appreciate the guidance. I did have to tweak some of the
functionality to make the test case pass reliably, as there were
still some races possible. I also saw that SBThread.Resume() seems
to occasionally result in a StopReason of eStopReasonNon. So I worked
around that by only including threads int expected output that the Resume
resulted in making it to our breakpoint. I have verified the test is
consistently passes by executing it on repeat 100 times,
Greg: Thanks for the suggestions for using std::set, and lldb:adrr_t.
The code is a lot cleaner now, and as you mentioned should perform faster.
I didn't notice any significant speed up with my 700 thread dump however.
https://reviews.llvm.org/D33426
Files:
include/lldb/Target/Thread.h
packages/Python/lldbsuite/test/functionalities/thread/num_threads/TestNumThreads.py
packages/Python/lldbsuite/test/functionalities/thread/num_threads/main.cpp
source/Commands/CommandObjectThread.cpp
source/Core/Debugger.cpp
source/Target/Thread.cpp
-------------- next part --------------
A non-text attachment was scrubbed...
Name: D33426.100529.patch
Type: text/x-patch
Size: 18181 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/lldb-commits/attachments/20170527/96412115/attachment-0001.bin>
More information about the lldb-commits
mailing list