summaryrefslogtreecommitdiffstats
path: root/lldb/test/functionalities
Commit message (Collapse)AuthorAgeFilesLines
...
* Mark the other test of TestFdLeak also as xfail to keep the bot green.Siva Chandra2015-05-021-0/+1
| | | | | | | | | | | | | | | | Summary: r235916 marked only one of the tests as xfail, but the other also has been failing intermitantly on the buildbot. Reviewers: chaoren Reviewed By: chaoren Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D9452 llvm-svn: 236366
* Add expectedFailureLinux to TestProcessAttachPavel Labath2015-04-301-2/+6
| | | | | | The test is skipped anyway due to timeout, but adding XFAIL improves grepability. llvm-svn: 236224
* Skip TestProcessAttach.py on LinuxPavel Labath2015-04-281-2/+2
| | | | | | | The test was already XFAILed. Changing this to skip, because the test timeouts and gets flagged as an error anyway. llvm-svn: 235979
* [TestProcessAttach] Decorate with expectedFailureLinuxSiva Chandra2015-04-271-0/+2
| | | | | | | | | | | | | | Summary: Link to PR: llvm.org/pr23360 Test Plan: dotest.py -p TestProcessAttach Reviewers: sivachandra Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D9310 llvm-svn: 235947
* XFail flakey test.Chaoren Lin2015-04-271-0/+1
| | | | llvm-svn: 235916
* Eliminate redundant Alias test and improve Common Short Spellings test ↵Adrian McCarthy2015-04-247-350/+20
| | | | | | http://reviews.llvm.org/D9268 llvm-svn: 235790
* Factor resolution of abbreviations and aliases so that they can be tested ↵Adrian McCarthy2015-04-231-164/+80
| | | | | | directly. http://reviews.llvm.org/D9033 llvm-svn: 235633
* Fix test expectation in TestNoreturnUnwindTamas Berghammer2015-04-231-3/+2
| | | | | | | | | | The test case lookinhg for the abort function in the stack trace. Previously it lookd for a function which ends with "abort" but on some system there are multiple such functions (e.g.: on android abort calls __libc_android_abort) what made the test fail. This CL change the behaviour to look for the abort function based on a fix list of names. llvm-svn: 235584
* Add decorator for signal test failing on FreeBSDEd Maste2015-04-221-0/+1
| | | | | | llvm.org/pr23318 llvm-svn: 235523
* XFAILing a single test in TestConcurrentEventsPavel Labath2015-04-221-0/+1
| | | | | | | apparently, TestConcurrentEvents is still not fixed. One test has failed on Linux i386 build. Will disable the failing test on i386 for now, and see how it goes.. llvm-svn: 235504
* Enable TestConcurrentEvents on LinuxPavel Labath2015-04-221-16/+0
| | | | | | | After the latest changes in NativeProcessLinux, these tests should be stable now. Please revert (and let me know) if any issue crops up. llvm-svn: 235502
* XFAIL tests that are failed on linux with gcc-4.9.2Ying Chen2015-04-215-1/+7
| | | | | | | | | | | | | | | | | | | Summary: - add decorator functions to xfail and skip test on specific os, architecture and version of comipler - xfail failing test with gcc-4.9.2 on linux - add one usage of skipIf function Test Plan: Run tests with different archs, and version of compilers to verify decorator function working as expected Run tests with gcc-4.9.2 and no failure reported Reviewers: sivachandra, ovyalov, vharron, chaoren Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D8851 llvm-svn: 235368
* Add Makefile for typedef_arrayYing Chen2015-04-201-0/+4
| | | | | | | | | | | | | | | | -Makefile was deleted by r235313 causing test failure of TestTypedefArray.py, add it back Summary: -Makefile was deleted by r235313 causing test failure of TestTypedefArray.py, add it back Test Plan: Run lldb test locally with change, TestTypedefArray.py passed and no regression observed. Reviewers: chaoren, sivachandra, vharron Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D9119 llvm-svn: 235346
* This patch implements several improvements to theSean Callanan2015-04-201-4/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | module-loading support for the expression parser. - It adds support for auto-loading modules referred to by a compile unit. These references are currently in the form of empty translation units. This functionality is gated by the setting target.auto-import-clang-modules (boolean) = false - It improves and corrects support for loading macros from modules, currently by textually pasting all #defines into the user's expression. The improvements center around including only those modules that are relevant to the current context - hand-loaded modules and the modules that are imported from the current compile unit. - It adds an "opt-in" mechanism for all of this functionality. Modules have to be explicitly imported (via @import) or auto-loaded (by enabling the above setting) to enable any of this functionality. It also adds support to the compile unit and symbol file code to deal with empty translation units that indicate module imports, and plumbs this through to the CompileUnit interface. Finally, it makes the following changes to the test suite: - It adds a testcase that verifies that modules are automatically loaded when the appropriate setting is enabled (lang/objc/modules-auto-import); and - It modifies lanb/objc/modules-incomplete to test the case where a module #undefs something that is #defined in another module. <rdar://problem/20299554> llvm-svn: 235313
* NativeProcessLinux: Merge operation and monitor threadsPavel Labath2015-04-201-1/+0
| | | | | | | | | | | | | | | | | Summary: This commit moves the functionality of the operation thread into the new monitor thread. This is required to avoid a kernel race between the two threads and I believe it actually makes the code cleaner. Test Plan: Ran the test suite a couple of times, no regressions. Reviewers: ovyalov, tberghammer, vharron Subscribers: tberghammer, lldb-commits Differential Revision: http://reviews.llvm.org/D9080 llvm-svn: 235304
* Make several test case arm32 compatibleTamas Berghammer2015-04-171-1/+3
| | | | llvm-svn: 235172
* Uses the target platform to determine the platform context.Robert Flack2015-04-171-1/+1
| | | | | | | | | | | | | | | Uses the target platform to determine the platform context to use. This fixes an early failure in some tests when running on a different remote target. Test Plan: ./dotest.py $DOTEST_OPTS -t -p TestGlobalVariables.py|TestSharedLib.py Running on macosx -> linux, this fails at a later stage in the test - rather than in registerSharedLibrariesWithTarget looking for a library without the correct "lib" prefix and ".so" suffix. Differential Revision: http://reviews.llvm.org/D9047 llvm-svn: 235164
* Fix a bug where argdumper would not launch inferiors correctly in the ↵Enrico Granata2015-04-171-0/+21
| | | | | | | | presence of arguments of the form word1\ word2 (vs. the quoted form "word1 word2") Fixes rdar://20493444 llvm-svn: 235157
* Fix TestPluginCommands for gcc.Chaoren Lin2015-04-161-1/+0
| | | | | | | | | | | | | | | | Summary: gcc requires that LDFLAGS come after DYLIB_OBJECTS. Test Plan: TestPluginCommands passes. Reviewers: sivachandra, pcc, clayborg Reviewed By: clayborg Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D9045 llvm-svn: 235137
* Fix the ConvenienceVariablesCase tests after r234993Ilia K2015-04-151-4/+1
| | | | llvm-svn: 235010
* Bug 23051 - Fix zombie processes after lldb-server testsIlia K2015-04-151-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Summary: This patch fixes the following bug: https://llvm.org/bugs/show_bug.cgi?id=23181 For some reason some lldb-server tests should be kicked using SIGHUP and SIGINT before termination, otherwise it will leave a zombie process. I think the reason is that the lldb-server will terminate a slave process if it gets the SIGHUP/SIGINT and if so it should be fixed in lldb-server. The solution is to terminate process like it does the pexpect (including the delayafterterminate interval). Also this patch reverts the following commits: * r234549 - Skip lldb-server tests according to bug 23181 * r234765 - Skip a few tests on OS X according to the bug 23181 * r234803 - Skip the TestGdbRemoteRegisterState.test_grp_register_save_restore_works_no_suffix_debugserver_dsym test on OS X according to the bug 23181 Test Plan: ``` $ ps | grep Z | grep a.out | wc -l 447 $ ./dosep.py --options "-v --executable $INSTALLDIR/bin/lldb" [...] $ ps | grep Z | grep a.out | wc -l 447 ``` Reviewers: jasonmolenda, clayborg, tberghammer Reviewed By: clayborg Subscribers: lldb-commits, dawn, tberghammer, clayborg, jasonmolenda Differential Revision: http://reviews.llvm.org/D9019 llvm-svn: 235008
* TestConvenienceVariables - fixed a Linux problemVince Harron2015-04-151-1/+5
| | | | | | | | | Test was waiting for wrong string on Linux. It is still marked as XFAIL because of an intermittent failure. Differential Revision: http://reviews.llvm.org/D8679 llvm-svn: 234993
* Remove gcc xfail for TestWatchpointMultipleThreads.Chaoren Lin2015-04-141-2/+0
| | | | llvm-svn: 234826
* [TestPluginCommands] Add skipIfGcc at the right place.Siva Chandra2015-04-141-1/+1
| | | | | | | | | | | | | | | | | | | Summary: The decorator @expectedFailureGcc was at the wrong place skipping this test all together. This patch removes it and adds skipIfGcc at the right place. Test Plan: dotest.py -C <gcc|clang> -p TestPluginCommands Reviewers: chying, chaoren Reviewed By: chaoren Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D9010 llvm-svn: 234821
* Skip libc++ data formmatting tests on Windows. libc++ hasn't been ported to ↵Adrian McCarthy2015-04-138-0/+8
| | | | | | windows yet. llvm-svn: 234794
* Missing `-lpthread` causes gcc test failure.Chaoren Lin2015-04-133-3/+0
| | | | | | | | | | | | | | | Summary: `-lpthread` was removed for `g++ -std=c++11` on Linux due to llvm.org/pr21553, but the original issue doesn't seem to be reproducible anymore. Even if it were, it had nothing to do with compiling inferiors. Reviewers: sbest, sivachandra, chying Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D8991 llvm-svn: 234770
* Skip a few tests on OS X according to the bug 23181Ilia K2015-04-131-0/+1
| | | | llvm-svn: 234765
* [TestFormatters, TestDataFormatterSynthVal] Mark as xfail.Siva Chandra2015-04-101-0/+1
| | | | | | | | | | | | | | | | Summary: This is to get the bots to go green while a robust solution to fix these tests is worked out. Reviewers: chaoren, tberghammer, clayborg Reviewed By: tberghammer, clayborg Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D8947 llvm-svn: 234625
* Check in missing file.Greg Clayton2015-04-101-0/+88
| | | | llvm-svn: 234609
* Fix a problem where 'process launch' was not correctly re-quoting arguments ↵Enrico Granata2015-04-102-0/+21
| | | | | | | | for the inferior process when handing them down for the actual launch This covers most of rdar://20490076, but leaves one corner case still open - namely the case where we try to have arguments of the form foo\ bar (unquoted, but slashed) go through argdumper llvm-svn: 234554
* Fix stepping a virtual thread when the python operating system was enabled.Greg Clayton2015-04-071-0/+69
| | | | | | | | | | | | The OperatingSystem plug-ins allow code to detect threads in memory and then say "memory thread 0x11111" is backed by the actual thread 1. You can then single step these virtual threads. A problem arose when thread specific breakpoints were used during thread plans where we would say "set a breakpoint on thread 0x11111" and we would hit the breakpoint on the real thread 1 and the thread IDs wouldn't match and we would get rid of the "stopped at breakpoint" stop info due to this mismatch. Code was added to ensure these events get forwarded and thus allow single stepping a memory thread to work correctly. Added a test case for this as well. <rdar://problem/19211770> llvm-svn: 234364
* TestRecursiveInferior fixed on LinuxVince Harron2015-04-031-4/+4
| | | | | | | | | | | | | | | | | Summary: Updated test to reflect that Linux and Darwin behave the same now. Removed @expectedFailureLinux for passing tests. Test Plan: run tests Reviewers: clayborg, sivachandra Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D8678 llvm-svn: 233989
* Fix a few more test suite errors where a cleanup lambda was calling ↵Greg Clayton2015-04-021-2/+2
| | | | | | self.runCmd() which requires the command returns successfully. Using self.dbg.HandleCommand() doesn't require success. llvm-svn: 233934
* Many many test failures after some recent changes. The problem is ↵Greg Clayton2015-04-027-14/+14
| | | | | | | | | | | | | | | | lldbtest.getPlatform() returns the "OS" of the selected platform's triple. This is "macosx" for desktop macosx and "ios" for iOS. It used to be "darwin". There was a lot of code that was checking "if self.getPlatform() == 'darwin'" which is not correct. I fixed this by adding a: lldbtest.platformIsDarwin() which returns true if the current platform's OS is "macosx", "ios" or "darwin". These three valid darwin are now returned by a static function: lldbtest.getDarwinOSTriples() Fixed up all places that has 'if self.getPlatform() == "darwin":' with "if self.platformIsDarwin()" and all instances of 'if self.getPlatform() != "darwin":' with "if not self.platformIsDarwin()". I also fixed some darwin decorator functions to do the right thing as well. llvm-svn: 233933
* Fix test expectation for aarch64 in several test caseTamas Berghammer2015-04-023-13/+8
| | | | | | | | | | | | These test cases check if they are able to read registers after the inferior is crashed. Previously they did it with reading the eax register what is only available on i386 and x86_64. Thic CL add code to do the check based on the target architecture (currently i386, x86_64 and aarch64 is supported) Differential revision: http://reviews.llvm.org/D8702 llvm-svn: 233907
* Update sys.platform switched behavior in tests to use self.getPlatform ↵Robert Flack2015-04-017-16/+16
| | | | | | | | | | | | | | | | | | | | | | (remote target platform) Uses target platform when determining which platform specific behavior to use or expect in tests. TestHelp.py was unchanged because this is asserting behavior of the local lldb binary. Test Plan: Run tests on different remote os. Several previously failing tests now pass: TestArrayTypes.py TestInferiorChanged.py TestInferiorCrashing.py TestIvarProtocols.py TestProcessIO.py TestPublicAPIHeaders.py TestRecursiveInferior.py Differential Revision: http://reviews.llvm.org/D8747 llvm-svn: 233805
* Make TestBreakpointConditions aarch64 compatibleTamas Berghammer2015-04-011-1/+4
| | | | llvm-svn: 233800
* Add missing makefile got test caseTamas Berghammer2015-04-011-0/+4
| | | | llvm-svn: 233797
* Enabled a bunch of tests on LinuxVince Harron2015-03-318-13/+3
| | | | | | | | | Removed expectedFailureLinux from failures that I was unable to reproduce, updated and improved some other comments near XFAIL tests Differential Revision: http://reviews.llvm.org/D8676 llvm-svn: 233716
* Fix TestSendSignal.py for remote.Chaoren Lin2015-03-311-20/+28
| | | | | | | | | | | | | | Summary: There is an extra eStateConnected before eStateRunning with remote. Reviewers: clayborg, ovyalov Reviewed By: clayborg, ovyalov Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D8714 llvm-svn: 233670
* Replace sys.platform skips in tests with @skip decorators which check ↵Robert Flack2015-03-30124-207/+207
| | | | | | | | | | | | | | | | against remote platform. Adds @skipIfPlatform and @skipUnlessPlatform decorators which will skip if / unless the target platform is in the provided platform list. Test Plan: ninja check-lldb shows no regressions. When running cross platform, tests which cannot run on the target platform are skipped. Differential Revision: http://reviews.llvm.org/D8665 llvm-svn: 233547
* Fix check in TestNoreturnUnwindTamas Berghammer2015-03-301-1/+1
| | | | llvm-svn: 233546
* Fix lld command on Windows for many tests.Adrian McCarthy2015-03-271-0/+1
| | | | llvm-svn: 233416
* Fix the remaining two test failures caused by re-ordering of teardown.Zachary Turner2015-03-262-5/+0
| | | | | | | | | Previously we were using teardown hooks in these two instances to shutdown processes. TestBase already deletes all targets in its own teardown, which will kill processes, so these steps weren't necessary. llvm-svn: 233308
* Fix RegisterCommandsTestCase and HelloWorldTestCase tests which hang on OS X ↵Ilia K2015-03-261-0/+4
| | | | | | after TestBase.tearDown() llvm-svn: 233279
* Destroy the attached process in tearDown() to fix ProcessAttachTestCase ↵Ilia K2015-03-261-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | tests on OS X This patch fixes the following: ``` 1: test_attach_to_process_by_id_with_dsym (TestProcessAttach.ProcessAttachTestCase) Test attach by process id ... ok 2: test_attach_to_process_by_id_with_dwarf (TestProcessAttach.ProcessAttachTestCase) Test attach by process id ... ok 3: test_attach_to_process_by_name_with_dsym (TestProcessAttach.ProcessAttachTestCase) Test attach by process name ... FAILURE 4: test_attach_to_process_by_name_with_dwarf (TestProcessAttach.ProcessAttachTestCase) Test attach by process name ... FAILURE ====================================================================== FAIL: test_attach_to_process_by_name_with_dsym (TestProcessAttach.ProcessAttachTestCase) Test attach by process name ---------------------------------------------------------------------- Traceback (most recent call last): File "/Users/IliaK/p/llvm/tools/lldb/test/lldbtest.py", line 462, in wrapper return func(self, *args, **kwargs) File "/Users/IliaK/p/llvm/tools/lldb/test/functionalities/process_attach/TestProcessAttach.py", line 35, in test_attach_to_process_by_name_with_dsym self.process_attach_by_name() File "/Users/IliaK/p/llvm/tools/lldb/test/functionalities/process_attach/TestProcessAttach.py", line 79, in process_attach_by_name self.runCmd("process attach -n s" + exe_name) File "/Users/IliaK/p/llvm/tools/lldb/test/lldbtest.py", line 2008, in runCmd msg if msg else CMD_MSG(cmd)) AssertionError: False is not True : Command 'process attach -n sProcessAttach' returns successfully Config=x86_64-clang ====================================================================== FAIL: test_attach_to_process_by_name_with_dwarf (TestProcessAttach.ProcessAttachTestCase) Test attach by process name ---------------------------------------------------------------------- Traceback (most recent call last): File "/Users/IliaK/p/llvm/tools/lldb/test/lldbtest.py", line 479, in wrapper return func(self, *args, **kwargs) File "/Users/IliaK/p/llvm/tools/lldb/test/functionalities/process_attach/TestProcessAttach.py", line 41, in test_attach_to_process_by_name_with_dwarf self.process_attach_by_name() File "/Users/IliaK/p/llvm/tools/lldb/test/functionalities/process_attach/TestProcessAttach.py", line 79, in process_attach_by_name self.runCmd("process attach -n s" + exe_name) File "/Users/IliaK/p/llvm/tools/lldb/test/lldbtest.py", line 2008, in runCmd msg if msg else CMD_MSG(cmd)) AssertionError: False is not True : Command 'process attach -n sProcessAttach' returns successfully Config=x86_64-clang ---------------------------------------------------------------------- ``` Failure-x86_64-clang-TestProcessAttach.ProcessAttachTestCase.test_attach_to_process_by_name_with_dsym.log: ``` [...] runCmd: process attach -n ProcessAttach runCmd failed! error: attach failed: more than one process named ProcessAttach: PID PARENT USER TRIPLE ARGUMENTS ====== ====== ========== ======================== ============================ 43752 43680 IliaK x86_64-apple-macosx /Users/IliaK/p/llvm/tools/lldb/test/functionalities/process_attach/ProcessAttach 43663 1 IliaK x86_64-apple-macosx /Users/IliaK/p/llvm/tools/lldb/test/functionalities/process_attach/ProcessAttach [...] ``` llvm-svn: 233272
* Fix StopHookForMultipleThreadsTestCase tests after r233098Ilia K2015-03-261-1/+1
| | | | llvm-svn: 233266
* Changed '-x'/'-xsize' to '-s'/'-size' when specifyingSean Callanan2015-03-263-13/+13
| | | | | | | | the size of a watchpoint. <rdar://problem/18184972> llvm-svn: 233237
* Add a test to make sure if you do:Greg Clayton2015-03-263-0/+104
| | | | | | | | | | | | % lldb /bin/echo (lldb) r 1 2 3 (lldb) r You get "1", "2", and "3" as arguments in the next re-run when no args are specified. This is behavior we do to match what GDB did and we need to test that we don't regress on it. <rdar://problem/20300941> llvm-svn: 233236
* Fix StdVBoolImplementation to handle large vectorsTamas Berghammer2015-03-251-1/+0
| | | | | | | | | | The previous implementation only read out the first element of the underlying storage array. Because of it only the first 32 (on x86) or the first 64 (on x86_64) element was displayed. Differential revision: http://reviews.llvm.org/D8585 llvm-svn: 233179
OpenPOWER on IntegriCloud