bcm5719-llvm/lldb/packages/Python/lldbsuite/test/functionalities/expr-entry-bp, branch meklort-10.0.1

bcm5719-llvm/lldb/packages/Python/lldbsuite/test/functionalities/expr-entry-bp, branch meklort-10.0.1 Project Ortega BCM5719 LLVM https://git.raptorcs.com/git/bcm5719-llvm/atom?h=meklort-10.0.1 2019-09-01T09:12:37+00:00 [lldb] Restructure test folders to match LLDB command hierarchy 2019-09-01T09:12:37+00:00 Raphael Isemann teemperor@gmail.com 2019-09-01T09:12:37+00:00 urn:sha1:29872606d220420d53fde7cc5e3bea15f8da62e7 Summary: As discussed on lldb-dev, this patch moves some LLDB tests into a hierarchy that more closely resembles the commands we use in the LLDB interpreter. This patch should only move tests that use the command interpreter and shouldn't touch any tests that primarily test the SB API. Reviewers: #lldb, jfb, JDevlieghere Reviewed By: #lldb, JDevlieghere Subscribers: dexonsmith, arphaman, JDevlieghere, lldb-commits Tags: #lldb Differential Revision: https://reviews.llvm.org/D67033 llvm-svn: 370605 [Target] Do not skip a stop on a breakpoint if a plan was completed 2018-11-30T09:45:52+00:00 Aleksandr Urakov aleksandr.urakov@jetbrains.com 2018-11-30T09:45:52+00:00 urn:sha1:9b087d2ce61e70e64c16ea5e88d68235148ba44f Summary: This patch fixes the next situation. On Windows clang-cl makes no stub before the main function, so the main function is located exactly on module entry point. May be it is the same on other platforms. So consider the following sequence: - set a breakpoint on main and stop there; - try to evaluate expression, which requires a code execution on the debuggee side. Such an execution always returns to the module entry, and the plan waits for it there; - the plan understands that it is complete now and removes its breakpoint. But the breakpoint site is still there, because we also have a breakpoint on entry; - StopInfo analyzes a situation. It sees that we have stopped on the breakpoint site, and it sees that the breakpoint site has owners, and no one logical breakpoint is internal (because the plan is already completed and it have removed its breakpoint); - StopInfo thinks that it's a user breakpoint and skips it to avoid recursive computations; - the program continues. So in this situation the program continues without a stop right after the expression evaluation. To avoid this an additional check that the plan was completed was added. Reviewers: jingham, zturner, boris.ulasevich Reviewed by: jingham Tags: #lldb Differential Revision: https://reviews.llvm.org/D53761 llvm-svn: 347974