summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test
Commit message (Collapse)AuthorAgeFilesLines
...
* 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
* Teach LLDB how to directly launch processes on the iOS simulatorEnrico Granata2015-11-058-5/+54
| | | | | | | | This allows for command-line debugging of iOS simulator binaries (as long as UI is not required, or a full UI simulator has previously been otherwise launched), as well as execution of the LLDB test suite on the iOS simulator This is known to compile on OSX 10.11 GM - feedback from people on other platforms and/or older versions of OSX as to the buildability of this code is greatly appreciated llvm-svn: 252112
* Add go data formatters.Ryan Brown2015-11-052-0/+75
| | | | | | Differential Revision: http://reviews.llvm.org/D13878 llvm-svn: 252109
* Handle keyword args on our patched Popen methods.Zachary Turner2015-11-041-4/+4
| | | | | | | | | | | Python 3 introduces the `timeout` keyword argument on Popen.wait(). If our patched version doesn't support keyword arguments, then when the internal Python implementation attempts to call wait() with the keyword argument, things will explode. Such as my head, after I finally figured out what was happening. llvm-svn: 252092
* Fix test infrastructure when using xunit output.Todd Fiala2015-11-041-2/+2
| | | | | | Our test reporting infrastructure needed module names to change based on the python package layout. llvm-svn: 252058
* Python 3 - Use universal_newlines when calling subprocess.check_outputZachary Turner2015-11-041-1/+1
| | | | | | | | | | | | | | | | | By default in Python 3, check_output() returns a program's output as an encoded byte sequence. This means it returns a Py3 `bytes` object, which cannot be compared to a string since it's a different fundamental type. Although it might not be correct from a purist standpoint, from a practical one we can assume that all output is encoded in the default locale, in which case using universal_newlines=True will decode it according to the current locale. Anyway, universal_newlines also has the nice behavior that it converts \r\n to \n on Windows platforms so this makes parsing code easier, should we need that. So it seems like a win/win. llvm-svn: 252025
* Fix an issue where LLDB would truncate summaries for string types without ↵Enrico Granata2015-11-041-1/+20
| | | | | | producing any evidence thereof llvm-svn: 252018
* Introduce seven.cmp_ and use it instead of cmpZachary Turner2015-11-031-1/+2
| | | | llvm-svn: 251982
* Remove `use_lldb_suite` from the package, and don't import it anymore.Zachary Turner2015-11-03392-413/+391
| | | | | | | | | | | | | | | | This module was originally intended to be imported by top-level scripts to be able to find the LLDB packages and third party libraries. Packages themselves shouldn't need to import it, because by the time it gets into the package, the top-level script should have already done this. Indeed, it was just adding the same values to sys.path multiple times, so this patch is essentially no functional change. To make sure it doesn't get re-introduced, we also delete the `use_lldb_suite` module from `lldbsuite/test`, although the original copy still remains in `lldb/test` llvm-svn: 251963
* Python 3 - Don't use `commands` module anymore.Zachary Turner2015-11-034-11/+11
| | | | | | | | | | The `commands` module was deprecated in 2.7 and removed in 3.x. As a workaround, we introduce a new module `seven` in lldbsuite.support, and write helper functions in there that delegate to the commands module if it is available, and re-implement their functionality for cases where it is not available. llvm-svn: 251959
* Fix flakyness in TestWatchLocationWithWatchSetPavel Labath2015-11-031-2/+4
| | | | | | Two threads in the test can hit the watchpoint simultaneously. Fix the test to account for that. llvm-svn: 251954
* Skip TestBacktraceAll on android-armTamas Berghammer2015-11-031-1/+4
| | | | | | | The android compiler can't compile the inferior because of an issue in the standard library. llvm-svn: 251951
* Leave TestAttachResume as flakey on linuxPavel Labath2015-11-031-0/+1
| | | | | | there must be (at least) one more race hidden there... llvm-svn: 251950
* Fix race during process detachPavel Labath2015-11-031-1/+0
| | | | | | | | | | | | | | | | Summary: The code which was preventing the usage of the OS plugin while detach is in progress also prevented us to update the thread list correctly. This resulted in an empty thread list, which confused the detaching logic. Change the condition do only do what it says (disable the usage of the OS plugin). Reviewers: clayborg, jingham Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D14201 llvm-svn: 251932
* Changes for Bug 25251Ravitheja Addepally2015-11-035-6/+223
| | | | | | | | | | | | | | | | | | | | | | | | | | Summary: The solution to bug 24074,rL249673 needed to parse the function information from the Dwarf in order to set the SymbolContext. For that, GetFunction was called for the parent in GetTypeForDIE, which parses the ChildParameters and in the flow, GetTypeForDIE was called for one of the sibling die and so an infinite loop was triggered by calling GetFunction repeatedly for the same function. The changes in this revision modify the GetTypeForDIE to only resolve the function context in the Type Lookup flow and so prevent the infinite loop. A testcase has also been added to check for regression in the future and a test vector had been added to the testcase of 24074. Reviewers: jingham, tberghammer, clayborg Differential Revision: http://reviews.llvm.org/D14202 llvm-svn: 251917
* Tighten up sys.path, and use absolute imports everywhere.Zachary Turner2015-11-03414-772/+815
| | | | | | | | | | | | | | | | | | | | For convenience, we had added the folder that dotest.py was in to sys.path, so that we could easily write things like `import lldbutil` from anywhere and any test. This introduces a subtle problem when using Python's package system, because when unittest2 imports a particular test suite, the test suite is detached from the package. Thus, writing "import lldbutil" from dotest imports it as part of the package, and writing the same line from a test does a fresh import since the importing module was not part of the same package. The real way to fix this is to use absolute imports everywhere. Instead of writing "import lldbutil", we need to write "import lldbsuite.test.util". This patch fixes up that and all other similar cases, and additionally removes the script directory from sys.path to ensure that this can't happen again. llvm-svn: 251886
* Fix usage of removed decorator in TestExpressionsPavel Labath2015-11-031-1/+1
| | | | llvm-svn: 251880
* Revert "Make new dotest.py executable"Pavel Labath2015-11-021-0/+0
| | | | | | This was a misunderstanding on my part. The new dotest.py is not meant to be executed directly. llvm-svn: 251863
* Revert "Remove the __import__ hack of lldbtest_config."Pavel Labath2015-11-021-2/+5
| | | | | | The hack still seems to be necessary. Putting it back in until we figure out why. llvm-svn: 251862
* This test case does not actually depend on Cocoa; Foundation is good enoguhEnrico Granata2015-11-022-2/+2
| | | | llvm-svn: 251861
* Move go expression tests to the new location.Ryan Brown2015-11-022-0/+134
| | | | llvm-svn: 251835
* [dosep] Fix-up callers of process_dir, after it got its argument removedPavel Labath2015-11-021-2/+2
| | | | llvm-svn: 251830
* Remove the __import__ hack of lldbtest_config.Zachary Turner2015-11-021-5/+2
| | | | | | | | I think the underlying problem was fixed by r251819, but I can't reproduce the problem. So this is to check whether it does in fact fix the problem. llvm-svn: 251822
* Make dosep correctly invoke the top-level script when forking outZachary Turner2015-11-022-6/+6
| | | | | | | | | | | | | | | | | | | | packages/Python/lldbsuite is now a Python package, and it relies on its __init__.py being called to do package-level initialization. If you exec packages/Python/lldbsuite/dotest.py directly, you won't get this package level initialization, and things will fail. But without this patch, this is exactly what dosep itself does. To launch the multi-processing fork, it was hardcoding a path to dotest.py and exec'ing it from inside the package. The fix here is to get the path of the top-level script, and then exec'ing that instead. A more robust solution would involve refactoring the code so that dosep execs some internal script that imports lldbsuite, but that's a bit more involved. Differential Revision: http://reviews.llvm.org/D14157 Reviewed by: Todd Fiala llvm-svn: 251819
* Handle the options and parameters separator in every MI commandHafiz Abid Qadeer2015-11-021-0/+4
| | | | | | | | | | | | | | | | | | | Summary: As per the following link, the "--" separator can appear between the options and parameters of any MI command. Previously this separator was only handled by the `-data-disassemble` MI command. I have moved the relevant code into `CMICmdBase` so that any MI command can handle the aforementioned separator. https://sourceware.org/gdb/onlinedocs/gdb/GDB_002fMI-Input-Syntax.html#GDB_002fMI-Input-Syntax Reviewers: ki.stfu Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D14197 llvm-svn: 251793
* Harden this test case to do the right thing in the face of compiler changesEnrico Granata2015-10-312-2/+8
| | | | llvm-svn: 251732
* Mark another TestEvents test as flaky on linuxPavel Labath2015-10-301-0/+1
| | | | | | | I don't think anything has changed recently - the test was always flaky, but only very rarely. Still, it is causing noise in the buildbots. llvm-svn: 251699
* Make new dotest.py executablePavel Labath2015-10-301-0/+0
| | | | llvm-svn: 251684
* Some test cases that need the lldbExec path were failing because lldbExec ↵Enrico Granata2015-10-301-1/+4
| | | | | | | | | | was turning out to be None even though it was being validly set by dotest.py It turns out that lldbtest_config was being imported locally to "lldbsuite.test" instead of globally, so when the test cases got individually brought by a global import via __import__ by unittest2, they did not see the lldbtest_config import, and ended up importing a new separate copy of it, with lldbExec unset This is a simple hackaround that brings lldbtest_config to global visibility and makes sure the configuration data is correctly shared llvm-svn: 251678
* Add a --offset option to memory read that allows one to specify, given a ↵Enrico Granata2015-10-292-0/+10
| | | | | | type, how many sizeof(type) bytes to speak before starting to read memory llvm-svn: 251668
* Give the test class it's own name (it was reusing the name from ↵Jim Ingham2015-10-291-1/+1
| | | | | | TestCompletions.py). llvm-svn: 251657
* Better handle the arguments common to all MI commands.Hafiz Abid Qadeer2015-10-291-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | Summary: I observed that eclipse was passing --thread-group for many other commands then we are currently handling. Looking at the MI documentation, the following link states that each MI command accept the --thread and --frame option. Looking at the GDB implementation, it seems that apart from these 2, --thread-group is also handled the same way. https://sourceware.org/gdb/onlinedocs/gdb/Context-management.html#Context-management So instead of handling those arguments in every comamnds, I have moved them into the base class and removed them from elsewhere. Now any command can use these arguments. The patch seems big but most of the changes are mechanical. Reviewers: ki.stfu Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D14177 llvm-svn: 251636
* Fix flakyness in TestChangeProcessGroupPavel Labath2015-10-291-3/+8
| | | | | | | | | | | The test was verifying that the pid of the child is not equal to its process group by searching for text substrings. This failed in the rare cases when the pid actually *was* a substring of the process group (even though they were not equal). Change the test to use SB API and do proper numeric comparisons. llvm-svn: 251626
* Leave TestAttachResume as flakey on linuxPavel Labath2015-10-291-0/+1
| | | | | | there must be (at least) one more race hidden there... llvm-svn: 251590
* Skip this test is the test suite is running in a mode where it has no ↵Enrico Granata2015-10-281-6/+9
| | | | | | WindowServer access llvm-svn: 251559
OpenPOWER on IntegriCloud