summaryrefslogtreecommitdiffstats
path: root/lldb/test/lang/cpp/dynamic-value
Commit message (Collapse)AuthorAgeFilesLines
* Move lldb/test to lldb/packages/Python/lldbsuite/test.Zachary Turner2015-10-285-504/+0
| | | | | | | | | | | This is the conclusion of an effort to get LLDB's Python code structured into a bona-fide Python package. This has a number of benefits, but most notably the ability to more easily share Python code between different but related pieces of LLDB's Python infrastructure (for example, `scripts` can now share code with `test`). llvm-svn: 251532
* Rename `lldb_shared` to `use_lldb_suite`.Zachary Turner2015-10-272-2/+2
| | | | llvm-svn: 251444
* Port the python api decorator to use test categoriesPavel Labath2015-10-262-3/+3
| | | | | | | | | | | | | | | | | | Summary: Per discussions on the mailing list, I have implemented a decorator which annotates individual test methods with categories. I have used this framework to replace the '-a' and '+a' command-line switches (now '-G pyapi' and '--skip-category pyapi') and the @python_api_test decorator (now @add_test_categories('pyapi')). The test suite now gives an error message suggesting the new options if the user specifies the deprecated +/-a switches. If the general direction is good, I will follow this up with other switches. Reviewers: tberghammer, tfiala, granata.enrico, zturner Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D14020 llvm-svn: 251277
* Add from __future__ import print_function everywhere.Zachary Turner2015-10-232-8/+12
| | | | | | | | | | | | | Apparently there were tons of instances I missed last time, I guess I accidentally ran 2to3 non-recursively. This should be every occurrence of a print statement fixed to use a print function as well as from __future__ import print_function being added to every file. After this patch print statements will stop working everywhere in the test suite, and the print function should be used instead. llvm-svn: 251121
* Update every test to import `lldb_shared`.Zachary Turner2015-10-222-16/+5
| | | | | | | | | | | | | | | | | | | | | This is necessary in order to allow third party modules to be located under lldb/third_party rather than under the test folder directly. Since we're already touching every test file anyway, we also go ahead and delete the unittest2 import and main block wherever possible. The ability to run a test as a standalone file has already been broken for some time, and if we decide we want this back, we should use unittest instead of unittest2. A few places could not have the import of unittest2 removed,because they depend on the unittest2.expectedFailure or skip decorators. Removing all those was orthogonal in spirit to the purpose of this CL, so the import of unittest2 remains in those files that were using it for its test decorators. Those can be addressed separately. llvm-svn: 251055
* Merge dwarf and dsym testsTamas Berghammer2015-09-302-102/+66
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Currently most of the test files have a separate dwarf and a separate dsym test with almost identical content (only the build step is different). With adding dwo symbol file handling to the test suit it would increase this to a 3-way duplication. The purpose of this change is to eliminate this redundancy with generating 2 test case (one dwarf and one dsym) for each test function specified (dwo handling will be added at a later commit). Main design goals: * There should be no boilerplate code in each test file to support the multiple debug info in most of the tests (custom scenarios are acceptable in special cases) so adding a new test case is easier and we can't miss one of the debug info type. * In case of a test failure, the debug symbols used during the test run have to be cleanly visible from the output of dotest.py to make debugging easier both from build bot logs and from local test runs * Each test case should have a unique, fully qualified name so we can run exactly 1 test with "-f <test-case>.<test-function>" syntax * Test output should be grouped based on test files the same way as it happens now (displaying dwarf/dsym results separately isn't preferable) Proposed solution (main logic in lldbtest.py, rest of them are test cases fixed up for the new style): * Have only 1 test fuction in the test files what will run for all debug info separately and this test function should call just "self.build(...)" to build an inferior with the right debug info * When a class is created by python (the class object, not the class instance), we will generate a new test method for each debug info format in the test class with the name "<test-function>_<debug-info>" and remove the original test method. This way unittest2 see multiple test methods (1 for each debug info, pretty much as of now) and will handle the test selection and the failure reporting correctly (the debug info will be visible from the end of the test name) * Add new annotation @no_debug_info_test to disable the generation of multiple tests for each debug info format when the test don't have an inferior Differential revision: http://reviews.llvm.org/D13028 llvm-svn: 248883
* [Windows] XFAIL test that depend on dynamic value types.Zachary Turner2015-09-021-0/+1
| | | | llvm-svn: 246669
* Enabled a bunch of tests on LinuxVince Harron2015-03-311-1/+0
| | | | | | | | | 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
* Replace sys.platform skips in tests with @skip decorators which check ↵Robert Flack2015-03-302-3/+3
| | | | | | | | | | | | | | | | 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
* Some more failure to bug trackingEnrico Granata2014-10-161-4/+2
| | | | llvm-svn: 219973
* Add decorator for FreeBSD DynamicValueTestCase failureEd Maste2014-04-071-0/+1
| | | | | | | Not yet root-caused, but I presume it is the same issue that affects Linux. llvm-svn: 205712
* rdar://16424649Enrico Granata2014-04-022-60/+0
| | | | | | | | Clean up the DynamicValueTestCase Namely, I split off the part of the test that validates child counts to a separate test llvm-svn: 205450
* Use continue instead of nextEnrico Granata2014-04-011-1/+1
| | | | llvm-svn: 205354
* Correctly set the working directory when launching processes for both local ↵Greg Clayton2013-12-132-2/+2
| | | | | | and remote targets. llvm-svn: 197266
* Massive test suite cleanup to stop everyone from manually having to compute ↵Greg Clayton2013-12-102-2/+2
| | | | | | | | | | "mydir" inside each test case. This has led to many test suite failures because of copy and paste where new test cases were based off of other test cases and the "mydir" variable wasn't updated. Now you can call your superclasses "compute_mydir()" function with "__file__" as the sole argument and the relative path will be computed for you. llvm-svn: 196985
* Remove decorators for llvm.org/pr17225Ed Maste2013-11-221-1/+0
| | | | | | This issue is no longer reproducible, presumably due to changes in clang. llvm-svn: 195458
* Workaround the DWARF info is anticipating the derived class assignment issue ↵Enrico Granata2013-10-311-2/+8
| | | | | | in this test case for now llvm-svn: 193821
* Marking dynamic value test as expected failure on Linux.Andrew Kaylor2013-10-311-0/+1
| | | | llvm-svn: 193809
* Fix dynamic value test to build correctly on Linux with C++11 features.Andrew Kaylor2013-10-311-2/+2
| | | | llvm-svn: 193793
* <rdar://problem/15045059>Enrico Granata2013-10-302-0/+55
| | | | | | | One of the things that dynamic typing affects is the count of children a type has Clear out the flag that makes us blindly believe the children count when a dynamic type change is detected llvm-svn: 193663
* test: Update FreeBSD failure decoratorsEd Maste2013-09-131-0/+1
| | | | | | | | | | | | | | | llvm.org/pr15261 missing size for static arrays llvm.org/pr15278 expressions generating signals llvm.org/pr15824 thread states aren't properly maintained llvm.org/pr16696 threaded inferior debugging not yet on FreeBSD llvm.org/pr17214 inline stepping fails on FreeBSD llvm.org/pr17225 Clang assertion failure llvm.org/pr17226 frame info lost after failed expression evaluation llvm.org/pr17228 test timeout The first three are existing Linux issues that also affect FreeBSD. llvm-svn: 190698
* <rdar://problem/13558484>Enrico Granata2013-04-111-1/+5
| | | | | | This makes the dynamic values test case work for both libc++ and libstdcpp llvm-svn: 179333
* Patch from Matt Kopec <matt.kopec@intel.com> to fix the problem that if two ↵Jim Ingham2012-10-161-1/+2
| | | | | | | | breakpoints were set on consecutive addresses, the continue from the first breakpoint would skip the second. llvm-svn: 166000
* Second batch of adding @dsym_test/@dwarf_test decorators to existing test cases.Johnny Chen2012-04-062-0/+6
| | | | | | | Plus some minor cleanup of test method names. Third and final batch is coming. llvm-svn: 154197
* fixing a macro name mismatch that was making our test case succeed for the ↵Enrico Granata2012-02-102-2/+4
| | | | | | wrong reason; plus a minor code change to the CPP side of the test which eases debugging efforts llvm-svn: 150213
* Fix compile time warnings for the inferior program.Johnny Chen2012-02-092-2/+2
| | | | llvm-svn: 150205
* Special build dictionary needs the same dictionary when specifying the ↵Johnny Chen2012-02-061-0/+4
| | | | | | after-the-test cleanup. llvm-svn: 149900
* Add regular C++ inheritance in addition to the virtual inheritance to ↵Johnny Chen2012-02-062-11/+37
| | | | | | | | TestCppValueCast.py. Plus mark the virtual inheritance test cases as expected failures. llvm-svn: 149891
* Add test cases for SBValue.Cast(SBType). The test logic needs more polishing.Johnny Chen2012-02-042-0/+198
| | | | llvm-svn: 149741
* Add SBValue::GetDynamicValue and SBValue::GetStaticValue API's.Jim Ingham2011-12-081-0/+9
| | | | | | <rdar://problem/10545069> llvm-svn: 146173
* Turn the EvaluateExpression (..., True) tests back on.Jim Ingham2011-10-071-4/+3
| | | | llvm-svn: 141375
* Centralize all of the type name code so that we always strip the leadingGreg Clayton2011-06-301-1/+1
| | | | | | | | "struct ", "class ", and "union " from the start of any type names that are extracted from clang QualType objects. I had to fix test suite cases that were expecting the struct/union/class prefix to be there. llvm-svn: 134132
* Move C++-related test directories to now reside under lang.Johnny Chen2011-06-253-0/+297
llvm-svn: 133878
OpenPOWER on IntegriCloud