bcm5719-llvm/lldb/test/python_api, branch meklort-10.0.1Project Ortega BCM5719 LLVMhttps://git.raptorcs.com/git/bcm5719-llvm/atom?h=meklort-10.0.12015-10-28T17:43:26+00:00Move lldb/test to lldb/packages/Python/lldbsuite/test.2015-10-28T17:43:26+00:00Zachary Turnerzturner@google.com2015-10-28T17:43:26+00:00urn:sha1:c432c8f856e0bd84de980a9d9bb2d31b06fa95b1
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
Changes for Bug 173842015-10-28T09:47:29+00:00Ravitheja Addepallyravitheja.addepally@intel.com2015-10-28T09:47:29+00:00urn:sha1:f546b411d01f5d320f6a840ea861b6f0c58eee96
Summary:
Virtual dynamic shared objects, or vdso files were
not loaded for Linux OS.In Bug 17384 the call
stack could not be unwinded from functions
residing in the vdso object.
This commit adds support for loading such files by
reading the Aux vectors since a vdso is invisibily
mapped to the inferiors address space and the
actual file is not present in the filesystem. The
presence of the vdso is detected by inspecting
the Aux vector for AT_SYSINFO_EHDR tag.
Reviewers: lldb-commits, ovyalov, tberghammer
Subscribers: lldb-commits
Differential Revision: http://reviews.llvm.org/D14118
llvm-svn: 251505
Rename `lldb_shared` to `use_lldb_suite`.2015-10-27T20:12:05+00:00Zachary Turnerzturner@google.com2015-10-27T20:12:05+00:00urn:sha1:0a0490b1520e96b728448b8c43ca873fcaa809dc
llvm-svn: 251444
Python3 - Change sys.maxint to sys.maxsize.2015-10-26T16:51:20+00:00Zachary Turnerzturner@google.com2015-10-26T16:51:20+00:00urn:sha1:da3dea612249f90218b6112ea18e574662367594
Python3 has no analogue to sys.maxint since ints in Python 3 have
arbitrary size. However, the distinction was not actually important
in any of these cases, and in a few cases using maxint was already
a bug to begin with.
llvm-svn: 251306
Convert `long` to `int`, and portably detect all integral types.2015-10-26T16:51:09+00:00Zachary Turnerzturner@google.com2015-10-26T16:51:09+00:00urn:sha1:f67f7e31e7231c488d29a36b31c2725ad86acdb6
llvm-svn: 251305
Convert deprecated unittest method names.2015-10-26T16:50:39+00:00Zachary Turnerzturner@google.com2015-10-26T16:50:39+00:00urn:sha1:210eb970de7fa9531f844e72074d1db662ff2b1e
Plural methods were long deprecated, and in Python 3 they are gone.
Convert to the actual supported method names.
llvm-svn: 251303
Port the python api decorator to use test categories2015-10-26T09:28:32+00:00Pavel Labathlabath@google.com2015-10-26T09:28:32+00:00urn:sha1:dc8b2d3d3aa4cedd66ee5b113ee8cc535f2c5a04
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.2015-10-23T17:04:29+00:00Zachary Turnerzturner@google.com2015-10-23T17:04:29+00:00urn:sha1:35d017f0fc38b53e31f1a44d07c3c142f5d3620b
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`.2015-10-22T20:06:20+00:00Zachary Turnerzturner@google.com2015-10-22T20:06:20+00:00urn:sha1:77db4a855239049488e09f28c6665fdb3b51ef90
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
Use six to portably handle module renames in Python 2 and 32015-10-21T17:48:52+00:00Zachary Turnerzturner@google.com2015-10-21T17:48:52+00:00urn:sha1:814236d6947dfcc4773517449da1e626e0472d3c
llvm-svn: 250915