This repository was archived by the owner on Apr 2, 2020. It is now read-only.
LLDB changes required for stable branch update #367
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This reverts commit 741ad64.
…iables""" This reverts commit 03a56e8.
not sure if the swift URL is correct, but it's a starting point.
been specified yet (either by the user, or by one of the lldb extensions like qHostInfo or qProcessInfo), and the target.xml includes a <architecture> tag specifying x86_64, set the architecture appropriately. I'm not sure what we can expect to see in the <architecture> tag, so I'm only doing this for x86_64 right now where I've seen "i386:x86_64" used. I've seen a target.xml from a jtag board that sends just "arm" because it doesn't know more specifically what type of board it is connected to... <rdar://problem/29908970> git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@322339 91177308-0d34-0410-b5e6-96231b3b80d8 (cherry picked from commit 54c53dc) (cherry picked from commit 4a3aef6)
(cherry picked from commit d104a7a)
… (PR35920) This test stresses expression evaluation support for template functions. Currently the support is rudimentary, and running this test causes assertion failures in clang. This test cannot be XFAIL'ed because the test harness treats assertion failures as unexpected events. For now, the test must be skipped. git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@322340 91177308-0d34-0410-b5e6-96231b3b80d8 (cherry picked from commit 95d1af6)
Summary: This used to be important when all tests were run in a single process, but that has no longer been the case for a while. Furthermore, this hook fails to build on new mac versions for several people, and it's not clear whether fixing it is worth the effort. Reviewers: jingham, clayborg, davide Subscribers: lldb-commits Differential Revision: https://reviews.llvm.org/D41871 git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@322167 91177308-0d34-0410-b5e6-96231b3b80d8 (cherry picked from commit 3a7b402)
Most of the watchpoint tests are organized into subtrees, so we can use the file-based .categories approach to annotate them. The exception are the concurrent_events tests, which needed to be annotated on a per-test basis. The motivation behind this is to provide an easy way to disable watchpoint tests on systems where the watchpoint functionality is not present/unreliable. git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@317004 91177308-0d34-0410-b5e6-96231b3b80d8 (cherry picked from commit d425de7) Conflicts: packages/Python/lldbsuite/test/functionalities/thread/concurrent_events/n_watch_n_break/TestConcurrentNWatchNBreak.py packages/Python/lldbsuite/test/functionalities/thread/concurrent_events/two_watchpoints_one_breakpoint/TestConcurrentTwoWatchpointsOneBreakpoint.py packages/Python/lldbsuite/test/functionalities/thread/concurrent_events/two_watchpoints_one_signal/TestConcurrentTwoWatchpointsOneSignal.py packages/Python/lldbsuite/test/test_categories.py
(cherry picked from commit 4fc71cc)
[Swift] Update for type reconstruction behavior change with inout parameters [4.1] (cherry picked from commit e60c019)
At some point we introduced CFLAGS_NO_ARCH internally, but then it disappeared, and we never passed -g to the compiler -- meaning there was no line table info, and we couldn't set breakpoints, etc.
TestSwiftFoundationTypeData was x-failed ago, but with the recent stdlib resilience changes it unexpectedly asserts. rdar://36649559
We were failing to get a symbol address if it was used anywhere else. Also log the offset address and not just the fact that it was asked for. <rdar://problem/36636614>
of a dSYM per-uuid plist that may be present (dsymutil does not create this plist, it is only added after the fact by additional tools) -- either the DBGBuildSourcePath + DBGSourcePath pair of k-v entries which give us the build-time and debug-time remapping, or the newer DBGSourcePathRemapping dictionary which may give us multiple remappings. I'm changing the order that we process these & add them to the list of source remappings. If the DBGSourcePathRemapping dict is present, it should be the first entries we will try. <rdar://problem/36481989> git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@322418 91177308-0d34-0410-b5e6-96231b3b80d8 (cherry picked from commit ea45f01) (cherry picked from commit 95b23ae)
Remove obsolete measurements. This check in requires at least 10.11 Reviewed: Jason Molenda, Jim Ingham <rdar://problem/37047106> Xcode Memory gauge should show the jetsam ledger footprint rather than anonymous git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@324013 91177308-0d34-0410-b5e6-96231b3b80d8
Make use of physical footprint as memory measurement.
It is unused, and the underlying llvm function has been removed as well. git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@324472 91177308-0d34-0410-b5e6-96231b3b80d8 (cherry picked from commit 7c6d16f)
The former is no longer necessary since we no longer produce ImplicitlyUnwrappedOptionalType. (cherry picked from commit 929beee)
This patch makes LLDB's clang module cache path customizable via settings set target.clang-modules-cache-path <path> and uses it in the LLDB testsuite to reuse the same location inside the build directory for LLDB and clang. Differential Revision: https://reviews.llvm.org/D43099 git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@324775 91177308-0d34-0410-b5e6-96231b3b80d8 (cherry picked from commit b230a16)
(cherry picked from commit f3c8ca5)
(cherry picked from commit 8c66781)
As of swiftlang/swift#14299, we should effectively no longer see this decl since we no longer generate IUO types. A follow-on PR actually removes this API completely: swiftlang/swift#14364 (cherry picked from commit 9fac2e9)
(cherry picked from commit 2352524)
(cherry picked from commit cb66786)
in TestBase::getBuildArtifact(). This NFC commit is in preparation for https://reviews.llvm.org/D42281 (compile the LLDB tests out-of-tree). Differential Revision: https://reviews.llvm.org/D42280 git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@323007 91177308-0d34-0410-b5e6-96231b3b80d8 (cherry picked from commit 6dbd36a)
This test was calling buildDwarf() in NO_DEBUG_INFO tests. It looks like the skeleton of lldbinrepl.py was copied from some other place that had debug info variants, but here we really build only one standard variant. This file could use a rework, but for now just call buildDefault instead of buildDwarf.
…-lldb into llvm-swift5-transition
…swift5-transition
…wnershipAttr." This reverts commit fc67949.
…ferenceOwnershipAttr."" This reverts commit 58531ad.
This reverts commit 1ed9f57.
This reverts commit 4bc5a83.
This reverts commit 32cf91e.
|
@swift-ci please test linux platform |
|
swiftlang/swift#15088 @swift-ci please clean test linux platform |
Summary: Right now the test client is not parsing register values correctly, which is manifesting itself in one test failing on 32-bit architectures (pr36013). This parses the information from the qRegisterInfo packets and stores it in the client, which will enable fixing the parsing in a follow up commit. I am also adding a new templated SendMessage overload, which enables one to send a message get a parsed response in a single call. Reviewers: eugene, davide Subscribers: lldb-commits Differential Revision: https://reviews.llvm.org/D43076 git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@324722 91177308-0d34-0410-b5e6-96231b3b80d8
Summary: The issue was that we were parsing the registers into 64-bit integers and the calling swapByteOrder without regard for the actual size of the register. This switches the test to use the RegisterValue class which tracks the register size, and knows how to initialize itself from a piece of memory (so we don't need to swap byte order ourselves). Reviewers: eugene, davide Subscribers: lldb-commits Differential Revision: https://reviews.llvm.org/D43376 git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@325511 91177308-0d34-0410-b5e6-96231b3b80d8
1 similar comment
1 similar comment
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.