summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/functionalities
Commit message (Collapse)AuthorAgeFilesLines
* Teach LLDB how to directly launch processes on the iOS simulatorEnrico Granata2015-11-054-0/+11
| | | | | | | | 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
* 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
* Remove `use_lldb_suite` from the package, and don't import it anymore.Zachary Turner2015-11-03164-164/+164
| | | | | | | | | | | | | | | | 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-032-4/+4
| | | | | | | | | | 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-033-0/+211
| | | | | | | | | | | | | | | | | | | | | | | | | | 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-03166-324/+340
| | | | | | | | | | | | | | | | | | | | 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
* 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
* 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
* Mark TestHelloWorld and TestInferiorAssert.py as XFAIL due llvm.org/pr25338.Oleksiy Vyalov2015-10-281-0/+4
| | | | llvm-svn: 251542
* Move lldb/test to lldb/packages/Python/lldbsuite/test.Zachary Turner2015-10-28552-0/+28036
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
OpenPOWER on IntegriCloud