summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test
Commit message (Collapse)AuthorAgeFilesLines
...
* Pass -fms-compatibility-version when building test inferiors.Zachary Turner2015-11-191-0/+3
| | | | | | | | | | | | | | | | | -fms-compatibility-version defaults to VS 2013. When using VS 2015, this will lead to compilation failures of the test inferiors in the C++ standard library for language conformance reasons. The fix here is to simply pass -fms-compatibility-version=19.0 when we detect that a VS 2015 compiler is present. Even though we're actually using clang to do the compilation, clang uses this same detection algorithm to determine the location of the standard library. So this check is tantanmount to saying "If clang is going to find MSVC 2015's standard library, then pass 19.0 for -fms-compatibility-version. llvm-svn: 253589
* [LLDB][MIPS] Fix lldbplatformutil.py FailureSagar Thakur2015-11-191-3/+9
| | | | | | | | | | | Patch by Nitesh Jain Summary: This patch check whether first register is readable. Subscribers: lldb-commits, mohit.bhakkad, sagar, bhushan Reviewers: clayborg, ovyalov, jaydeep Differential: http://reviews.llvm.org/D14635 llvm-svn: 253555
* [TestExitDuringStep] Adjust after a recent type map change.Siva Chandra2015-11-181-1/+2
| | | | | | | | | | Reviewers: zturner Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D14784 llvm-svn: 253505
* Support unix-abstract-connect scheme as platform url in lldb testsuiteYing Chen2015-11-182-4/+11
| | | | | | | | | | Reviewers: ovyalov Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D14765 llvm-svn: 253488
* Fix some issues with swig & string conversion.Zachary Turner2015-11-183-3/+12
| | | | | | | | | | | | | | | | | | | | This patch fixes two issues: 1) Popen needs to be used with universal_newlines=True by default. This elicits automatic decoding from bytes -> string in Py3, and has no negative effects in other Py versions. 2) The swig typemaps for converting between string and (char*, int) did not work correctly when the length of the string was 0, indicating an error. In this case we would try to construct a string from uninitialized data. 3) Ironically, the bug mentioned in #2 led to a test passing on Windows that was actually broken, because the test was written such that the assertion was never even getting checked, so it passed by default. So we additionally fix this test to also fail if the method errors. By fixing this test it's now broken on Windows, so we also xfail it. llvm-svn: 253487
* [LLDB][MIPS] Fix TestDisassembleBreakpoint.py for MIPSSagar Thakur2015-11-181-2/+6
| | | | | | | | | | | Patch by Nitesh Jain Summary: The break is opcode for breakpoint instruction. Subscribers: lldb-commits, mohit.bhakkad, sagar, bhushan Reviewers: clayborg, ovyalov, jaydeep Differential: http://reviews.llvm.org/D14634 llvm-svn: 253445
* [MIPS][LLDB]Fix TestBreakpointCondition.py for MIPSSagar Thakur2015-11-181-3/+6
| | | | | | | | | | | | | Patch by Nitesh Jain Summary: The self.getArchitecture() returns the architecture based on the value of -A flag passed to dotest.py script. There are many possible values for MIPS to this option (like mips32r2, mips32r6, mips64, mips64r2,.... ). This patch uses re.match(mips,arch) to check if architecture string starts with mips. Subscribers: lldb-commits, mohit.bhakkad, sagar, bhushan, jaydeep Reviewers: clayborg, ovyalov Differential: http://reviews.llvm.org/D14493 llvm-svn: 253444
* Add the ability (through the SB API & command line) to specify an addressJim Ingham2015-11-173-0/+105
| | | | | | | | breakpoint as "file address" so that the address breakpoint will track that module even if it gets loaded in a different place. Also fixed the Address breakpoint resolver so that it handles this tracking correctly. llvm-svn: 253308
* Python 3 - Skip a certain test for a particular (swig,python) combo.Zachary Turner2015-11-162-1/+10
| | | | | | | | | | | Current versions of SWIG have a bug with Python 3 that causes Python to assert when iterating over a generator. This patch skips the test for the right combination of Python version and SWIG version. I'm attempting to upstream a patch to SWIG to fix this in a subsequent as-of-yet unreleased version, but I don't know how long that will take. llvm-svn: 253273
* Re-Apply "Add a "not_in()" function you can apply to the list type arguments ↵Ying Chen2015-11-162-4/+19
| | | | | | | | | | | | | | | | | to expectedFailureAll ..." with fix Summary: - Re-Commit r253106 - Initialize self.debug_info in Base::setUp() - Fix argument order when calling check_list_or_lambda for compiler Reviewers: jingham Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D14673 llvm-svn: 253272
* Add the ability to xfail or skip based on swig / python version.Zachary Turner2015-11-161-11/+54
| | | | llvm-svn: 253263
* Revert "Add a "not_in()" function you can apply to the list type arguments ↵Pavel Labath2015-11-162-21/+4
| | | | | | | | to expectedFailureAll to reverse" This reverts commit r253106. llvm-svn: 253197
* Uniquify all the type X delete commands via one common base classEnrico Granata2015-11-141-1/+1
| | | | | | This removes a lot of code, which is A Good Thing(TM) llvm-svn: 253140
* Add a "not_in()" function you can apply to the list type arguments to ↵Jim Ingham2015-11-142-4/+21
| | | | | | | | expectedFailureAll to reverse the sense of the test. llvm-svn: 253106
* Fixed a testcase problem where disassembly would fail for nameless functions.Sean Callanan2015-11-131-1/+2
| | | | llvm-svn: 253101
* Change the test to use the instruction list to get the consecutive addresses ↵Jim Ingham2015-11-131-18/+9
| | | | | | | | to break on. Rerunning was being foiled by ASLR. llvm-svn: 253094
* Re-XFAIL two more tests I missedPavel Labath2015-11-131-0/+2
| | | | llvm-svn: 253042
* Re-add XFAILs to two testsPavel Labath2015-11-132-0/+2
| | | | | | | these decorators were two of many removed in r253026. Unlike others, these tests still seem to be failing... llvm-svn: 253034
* Fix multiple symbol lookup in the same namespaceEugene Leviant2015-11-132-8/+44
| | | | llvm-svn: 253028
* Remove a broken hack from Scalar::ULongLong and fix a testTamas Berghammer2015-11-131-2/+2
| | | | | | | | | | | | | | | | Change Test-rdar-12481949.py to expect GetValueAsUnsigned() to return 0xffffffff if the variable is an int32_t (signed, 4 byte integer) with value of -1. The previous expectation where we expected the value to be 0xffffffffffffffff doesn't make sense as nothing explains why we would treat it as an 8 byte value. This CL also removes a hack from Scalar::ULongLong what was most likely added to get this test passing as it only worked in case the value of the variable is -1 and didn't make any sense even in that case. Differential revision: http://reviews.llvm.org/D14611 llvm-svn: 253027
* Fix to solve Bug 23139 & Bug 23560Abhishek Aggarwal2015-11-139-17/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Summary: - Reason of both bugs: 1. For the very first frame, Unwinder doesn't check the validity of Full UnwindPlan before creating StackFrame from it: When 'process launch' command is run after setting a breakpoint in inferior, the Unwinder runs and saves only Frame 0 (the frame in which breakpoint was set) in thread's StackFrameList i.e. m_curr_frames_sp. However, it doesn't check the validity of the Full UnwindPlan for this frame by unwinding 2 more frames further. 2. Unwinder doesn't update the CFA value of Cursor when Full UnwindPlan fails and FallBack UnwindPlan succeeds in providing valid CFA values for frames: Sometimes during unwinding of stack frames, the Full UnwindPlan inside the RegisterContextLLDB object may fail to provide valid CFA values for these frames. Then the Fallback UnwindPlan is used to unwind the frames. If the Fallback UnwindPlan succeeds, then it provides a valid new CFA value. The RegisterContextLLDB::m_cfa field of Cursor object is updated during the Fallback UnwindPlan execution. However, UnwindLLDB misses the implementation to update the 'cfa' field of this Cursor with this valid new CFA value. - This patch fixes both these issues. - Remove XFAIL in test files corresponding to these 2 Bugs Change-Id: I932ea407545ceee2d628f946ecc61a4806d4cc86 Signed-off-by: Abhishek Aggarwal <abhishek.a.aggarwal@intel.com> Reviewers: jingham, lldb-commits, jasonmolenda Subscribers: lldb-commits, ovyalov, tberghammer Differential Revision: http://reviews.llvm.org/D14226 llvm-svn: 253026
* Implement RegisterContext for Mini Dumps.Adrian McCarthy2015-11-121-0/+14
| | | | | | Differential Revision: http://reviews.llvm.org/D14591 llvm-svn: 252950
* [test] Fix comment.Dawn Perchik2015-11-121-1/+1
| | | | llvm-svn: 252831
* Marked test_qRegisterInfo_returns_{one_valid_result,all_valid_results} XFAIL ↵Todd Fiala2015-11-111-0/+2
| | | | | | | | | on Darwin. Tracked by: https://llvm.org/bugs/show_bug.cgi?id=25486 llvm-svn: 252707
* Bump up test timeout interval on Darwin from 4 to 6 minutes.Todd Fiala2015-11-111-0/+3
| | | | | | | We have several tests that TIMEOUT under heavy load but just need a bit more time to complete. llvm-svn: 252703
* Mark TestCompletion.py test_symbol_name_dwarf XFAIL on Darwin.Todd Fiala2015-11-111-0/+1
| | | | | | | | | | This test fails most of the time when run under heavy load. The dsym variant doesn't seem to be failing. Tracking XFAIL marker with: https://llvm.org/bugs/show_bug.cgi?id=25485 llvm-svn: 252702
* Mark TestTerminal.py as XFAIL on OS X.Todd Fiala2015-11-111-0/+1
| | | | | | | See the following tracking bug: https://llvm.org/bugs/show_bug.cgi?id=25484 llvm-svn: 252699
* Updated a relative path in Makefile.rules to reflect the new testsuite location.Sean Callanan2015-11-101-1/+1
| | | | llvm-svn: 252657
* Updated lldb_pylint_helper to work with recent Python package changes.Todd Fiala2015-11-101-15/+27
| | | | llvm-svn: 252642
* This test is now passing on DarwinEnrico Granata2015-11-101-1/+0
| | | | llvm-svn: 252637
* Mark TestMiInterpreterExec.test_lldbmi_thread_continue as flaky on linuxPavel Labath2015-11-101-0/+1
| | | | llvm-svn: 252596
* Avoid sending bare '*' and '}' in an lldb-server packetTim Northover2015-11-092-0/+32
| | | | | | | | | | They get treated as special RLE encoding symbols and packets get corrupted. Most other packet types already know about this apparently, but QEnvironment missed these two. Should fix PR25300. llvm-svn: 252521
* Add --curses shortcut for specifying the curses-based test results formatter.Todd Fiala2015-11-093-1/+13
| | | | | | | This commit closes the following review: http://reviews.llvm.org/D14488 llvm-svn: 252498
* Fix up curses_results.py for new package specification requirement.Todd Fiala2015-11-091-1/+1
| | | | | | | This was breaking but probably missed since it is currently infrequently used. llvm-svn: 252438
* Add SBType::IsAnonymousType() and relative plumbing in the debugger internalsEnrico Granata2015-11-072-0/+11
| | | | | | | | For language that support such a thing, this API allows to ask whether a type is anonymous (i.e. has been given no name) Comes with test case llvm-svn: 252390
* Python 3 - Don't use unbuffered I/O in text mode.Zachary Turner2015-11-071-2/+2
| | | | | | | | This is unsupported in Python 3. This could also have been fixed by using "wb" instead of "w", but it doesn't seem like writing the session log absolutely *needs* to be unbuffered. llvm-svn: 252381
* Make the language specifier to "break set" actually filter the names by ↵Jim Ingham2015-11-065-0/+112
| | | | | | | | | | | | | their language. So for instance: break set -l c++ -r Name will only break on C++ symbols that match Name, not ObjC or plain C symbols. This also works for "break set -n" and there are SB API's to pass this as well. llvm-svn: 252356
* Fixed another issue with wrong case in #import.Sean Callanan2015-11-061-1/+1
| | | | llvm-svn: 252354
* Fix Linux tests after r252348.Chaoren Lin2015-11-061-0/+1
| | | | llvm-svn: 252353
* Fixed a problem where a test case referred to aSean Callanan2015-11-061-1/+1
| | | | | | wrongly-capitalized header. llvm-svn: 252351
* Python 3 - Port use of string.maketrans and don't use sets.Set.Zachary Turner2015-11-062-4/+5
| | | | | | | | | | `sets.Set` has been deprecated in favor of `set` since 2.6, and `string.maketrans` has to be special cased. In Python 3 there is `str.maketrans`, `bytes.maketrans`, and `bytearray.maketrans` and you have to choose the correct one. So we need to introduce a runtime version check at this site. llvm-svn: 252348
* Python 3 - Use the exec function, not the exec statement.Zachary Turner2015-11-062-2/+4
| | | | | | exec statement is gone in Python 3, this version works in both. llvm-svn: 252347
* Don't use module internal implementation details in our decorators.Zachary Turner2015-11-061-8/+4
| | | | | | | | | | | | | | | | | We tried implementing something akin to a conditionalExpectedFailure decorator for unittest2. We did this by making use of some implementation details of the unittest2 module. In an effort to make this work with unittest, this patch removes the reliance on the implementation details. I have a hard time wrapping my head around how this all works with the deeply nested decorators, but the spirit of the patch here is to do do the following: If the condition function is true, use the original unittest2.expectedFailure decorator. Otherwise don't use any decorator, just call the test function. Differential Revision: http://reviews.llvm.org/D14406 Reviewed By: tberghammer, labath llvm-svn: 252326
* Make Windows always use multiprocessing-pool.Zachary Turner2015-11-061-5/+4
| | | | | | | | | We still see "Too many file handles" errors on Windows even with lower numbers of cores. It's not clear what the right balance is, and the bar seems to move as more tests get added. So just use the strategy that works until we can investigate more deeply. llvm-svn: 252325
* Another import fix for OS X.Chaoren Lin2015-11-051-1/+1
| | | | llvm-svn: 252230
* Fix OS X tests.Chaoren Lin2015-11-051-1/+1
| | | | llvm-svn: 252218
* Python 3 - Turn on absolute imports, and fix existing imports.Zachary Turner2015-11-0517-53/+130
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Absolute imports were introduced in Python 2.5 as a feature (e.g. from __future__ import absolute_import), and made default in Python 3. When absolute imports are enabled, the import system changes in a couple of ways: 1) The `import foo` syntax will *only* search sys.path. If `foo` isn't in sys.path, it won't be found. Period. Without absolute imports, the import system will also search the same directory that the importing file resides in, so that you can easily import from the same folder. 2) From inside a package, you can use a dot syntax to refer to higher levels of the current package. For example, if you are in the package lldbsuite.test.utility, then ..foo refers to lldbsuite.test.foo. You can use this notation with the `from X import Y` syntax to write intra-package references. For example, using the previous locationa s a starting point, writing `from ..support import seven` would import lldbsuite.support.seven Since this is now the default behavior in Python 3, this means that importing from the same directory with `import foo` *no longer works*. As a result, the only way to have portable code is to force absolute imports for all versions of Python. See PEP 0328 [https://www.python.org/dev/peps/pep-0328/] for more information about absolute and relative imports. Differential Revision: http://reviews.llvm.org/D14342 Reviewed By: Todd Fiala llvm-svn: 252191
* Fix TestGoFormatters.py.Chaoren Lin2015-11-051-3/+2
| | | | llvm-svn: 252133
* Python 3 - Don't use `os.path.walk`, it's removed in Py3.Zachary Turner2015-11-051-4/+2
| | | | | | | | It was deprecated even in 2.7, but not removed until 3.x. os.walk provides all of the same functionality and is the correct way to do this now. llvm-svn: 252127
* Python 3 - Use universal_newlines=True in subprocess.Popen.Zachary Turner2015-11-051-0/+2
| | | | | | | | | | | This follows the spirit of a previous patch which did essentially the same thing. In Python 3, when you use Popen.communicate(), you get back a bytes object which cannot normally be treated as a string. We could decode this manually, but universal_newlines=True does this automatically, and there's no disadvantage to doing so even on Python 2. So just enable it always. llvm-svn: 252126
OpenPOWER on IntegriCloud