[lldb/test] Disable TestStringLiteralExpr.test on WindowsThis test, introduced by b042d15d2e39eea528c51a30fe637b9ea84250d3, fails onhttps://lab.llvm.org/buildbot/#/builders/83/builds/20933/steps/7
[lldb/test] Disable TestStringLiteralExpr.test on WindowsThis test, introduced by b042d15d2e39eea528c51a30fe637b9ea84250d3, fails onhttps://lab.llvm.org/buildbot/#/builders/83/builds/20933/steps/7/logs/stdiobut succeeds on other targets, see for instancehttps://lab.llvm.org/buildbot/#/builders/68/builds/35462/steps/6/logs/stdioThis test is not be arch specific, just disabling it on Windows.
show more ...
[lldb/test] Add Shell/Expr/TestStringLiteralExpr.testThis test should exercise the usage of expressions containingstring literals and ensure that lldb doesn't crash.Differential Revision: https:
[lldb/test] Add Shell/Expr/TestStringLiteralExpr.testThis test should exercise the usage of expressions containingstring literals and ensure that lldb doesn't crash.Differential Revision: https://reviews.llvm.org/D129261
[lldb] [test] Skip Expr/nodefaultlib.cpp test if LD_PRELOAD Is usedSome LD_PRELOAD-ed libraries tend to interact badly with --nodefaultlib,particularly Gentoo sandbox. Do not run this test if LD_
[lldb] [test] Skip Expr/nodefaultlib.cpp test if LD_PRELOAD Is usedSome LD_PRELOAD-ed libraries tend to interact badly with --nodefaultlib,particularly Gentoo sandbox. Do not run this test if LD_PRELOAD ispresent in the running environment.Differential Revision: https://reviews.llvm.org/D107701
[lldb] More memory allocation test fixesXFAIL nodefaultlib.cpp on darwin - the test does not pass thereXFAIL TestGdbRemoteMemoryAllocation on windows - memory is allocatedwith incorrect permissi
[lldb] More memory allocation test fixesXFAIL nodefaultlib.cpp on darwin - the test does not pass thereXFAIL TestGdbRemoteMemoryAllocation on windows - memory is allocatedwith incorrect permissions
[lldb-server][linux] Add ability to allocate memoryThis patch adds support for the _M and _m gdb-remote packets, which(de)allocate memory in the inferior. This works by "injecting" am(un)map sysc
[lldb-server][linux] Add ability to allocate memoryThis patch adds support for the _M and _m gdb-remote packets, which(de)allocate memory in the inferior. This works by "injecting" am(un)map syscall into the inferior. This consists of:- finding an executable page of memory- writing the syscall opcode to it- setting up registers according to the os syscall convention- single stepping over the syscallThe advantage of this approach over calling the mmap function is thatthis works even in case the mmap function is buggy or unavailable. Thedisadvantage is it is more platform-dependent, which is why this patchonly works on X86 (_32 and _64) right now. Adding support for otherlinux architectures should be easy and consist of defining theappropriate syscall constants. Adding support for other OSes depends onthe its ability to do a similar trick.Differential Revision: https://reviews.llvm.org/D89124
[lldb] Make expect_expr fall back to the dummy target if no target is selectedSummary:Currently expect_expr will not run the expression if no target is selected. Thispatch changes this behavior
[lldb] Make expect_expr fall back to the dummy target if no target is selectedSummary:Currently expect_expr will not run the expression if no target is selected. Thispatch changes this behavior so that expect_expr will instead fall back to thedummy target similar to what the `expression` command is doing. This way wedon't have to compile an empty executable to be able to use `expect_expr` (whichis a waste of resources for tests that just test generic type system features).As a test I modernized the TestTypeOfDeclTypeExpr into a Python test +expect_expr (as it relied on the dummy target fallback of the expressioncommand).Reviewers: labath, JDevlieghereReviewed By: labathSubscribers: abidhDifferential Revision: https://reviews.llvm.org/D83388
[lldb/lit] Introduce %clang_host substitutionsSummary:This patch addresses an ambiguity in how our existing tests invoke thecompiler. Roughly two thirds of our current "shell" tests invoke theco
[lldb/lit] Introduce %clang_host substitutionsSummary:This patch addresses an ambiguity in how our existing tests invoke thecompiler. Roughly two thirds of our current "shell" tests invoke thecompiler to build the executables for the host. However, there is alsoa significant number of tests which don't build a host binary (becausethey don't need to run it) and instead they hardcode a certain target.We also have code which adds a bunch of default arguments to the %clangsubstitutions. However, most of these arguments only really make sensefor the host compilation. So far, this has worked mostly ok, because thearguments we were adding were not conflicting with the target-hardcodingtests (though they did provoke an occasional "argument unused" warning).However, this started to break down when we wanted to usetarget-hardcoding clang-cl tests (D69031) because clang-cl has asubstantially different command line, and it was getting very confusedby some of the arguments we were adding on non-windows hosts.This patch avoid this problem by creating separate %clang(xx,_cl)_hostsubstutitions, which are specifically meant to be used for compilinghost binaries. All funny host-specific options are moved there. Toensure that the regular %clang substitutions are not used for compilinghost binaries (skipping the extra arguments) I employ a littlehac^H^H^Htrick -- I add an invalid --target argument to the %clangsubstitution, which means that one has to use an explicit --target inorder for the compilation to succeed.Reviewers: JDevlieghere, aprantl, mstorsjo, espindolaSubscribers: emaste, arichardson, MaskRay, jfb, lldb-commitsTags: #lldbDifferential Revision: https://reviews.llvm.org/D69619
Re-land "[test] Split LLDB tests into API, Shell & Unit"The original patch got reverted because it broke `check-lldb` on a cleanbuild. This fixes that.llvm-svn: 374201
Revert [test] Split LLDB tests into API, Shell & Unitas it appears to have broken check-lldb.This reverts r374184 (git commit 22314179f0660c172514b397060fd8f34b586e82)llvm-svn: 374187
[test] Split LLDB tests into API, Shell & UnitLLDB has three major testing strategies: unit tests, tests that exercisethe SB API though dotest.py and what we currently call lit tests. Thelater is
[test] Split LLDB tests into API, Shell & UnitLLDB has three major testing strategies: unit tests, tests that exercisethe SB API though dotest.py and what we currently call lit tests. Thelater is rather confusing as we're now using lit as the driver for allthree types of tests. As most of this grew organically, the directorystructure in the LLDB repository doesn't really make this clear.The 'lit' tests are part of the root and among these tests there's aUnit and Suite folder for the unit and dotest-tests. This layout makesit impossible to run just the lit tests.This patch changes the directory layout to match the 3 testingstrategies, each with their own directory and their own configurationfile. This means there are now 3 directories under lit with 3corresponding targets: - API (check-lldb-api): Test exercising the SB API. - Shell (check-lldb-shell): Test exercising command line utilities. - Unit (check-lldb-unit): Unit tests.Finally, there's still the `check-lldb` target that runs all three testsuites.Finally, this also renames the lit folder to `test` to match the LLVMrepository layout.Differential revision: https://reviews.llvm.org/D68606llvm-svn: 374184