| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
| |
llvm-svn: 252831
|
| |
|
|
|
|
|
|
| |
This had been relegated to a simple forwarding function, so just
delete it in preparation of migrating all of these functions out
of python-wrapper.swig.
llvm-svn: 252803
|
| |
|
|
|
|
|
|
|
| |
This only begins to port python-wrapper.swig over. Since this
code can be pretty hairy, I plan to do this incrementally over a
series of patches, each time removing or converting more code
over to the PythonDataObjects code.
llvm-svn: 252788
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds PythonTuple and PythonCallable classes to PythonDataObjects.
Additionally, unit tests are provided that exercise this functionality,
including invoking manipulating and checking for validity of tuples,
and invoking and checking for validity of callables using a variety
of different syntaxes.
The goal here is to eventually replace the code in python-wrapper.swig
that directly uses the Python C API to deal with callables and name
resolution with this code that can be more easily tested and debugged.
llvm-svn: 252787
|
| |
|
|
| |
llvm-svn: 252767
|
| |
|
|
| |
llvm-svn: 252765
|
| |
|
|
| |
llvm-svn: 252764
|
| |
|
|
|
|
|
|
|
| |
on Darwin.
Tracked by:
https://llvm.org/bugs/show_bug.cgi?id=25486
llvm-svn: 252707
|
| |
|
|
|
|
|
| |
We have several tests that TIMEOUT under heavy load but just need a bit
more time to complete.
llvm-svn: 252703
|
| |
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
| |
See the following tracking bug:
https://llvm.org/bugs/show_bug.cgi?id=25484
llvm-svn: 252699
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It used to be a unique pointer, and there could be a case where ClangASTSource
held onto a copy of the pointer but Target::Destroy destroyed the unique pointer
in the mean time.
I also ensured that there is a validity check on the target (which confirms that
a ClangASTImporter can be generated) before the target's shared pointer is
copied into ClangASTSource.
This race condition caused a crash if Target::Destroy was called and then later
the target objecct was deleted.
llvm-svn: 252665
|
| |
|
|
|
|
|
|
|
|
| |
are "nil" (not pointing to anything) or uninitialized (never made to point at anything)
This latter determination may or may not be possible on a per-language basis; and neither is mandatory to implement for any language
Use this knowledge in the ValueObjectPrinter to generalize the notion of IsObjCNil() and the respective printout
llvm-svn: 252663
|
| |
|
|
| |
llvm-svn: 252657
|
| |
|
|
| |
llvm-svn: 252655
|
| |
|
|
| |
llvm-svn: 252642
|
| |
|
|
| |
llvm-svn: 252638
|
| |
|
|
| |
llvm-svn: 252637
|
| |
|
|
|
|
| |
Differential Revision: http://reviews.llvm.org/D13819
llvm-svn: 252624
|
| |
|
|
|
|
|
|
|
|
| |
CompilerDecl class to do the job in an abstract way.
Fixed a crash that would happen if you tried to get the name of a constructor or destructor by calling "getDeclName()" instead of calling getName() (which would assert and crash).
Added the ability to get function arguments names from SBFunction.
llvm-svn: 252622
|
| |
|
|
| |
llvm-svn: 252605
|
| |
|
|
| |
llvm-svn: 252596
|
| |
|
|
|
|
|
|
| |
Add support for the new dyld shared cache format on
ios etc devices.
Small changes for classifying ObjC metadata symbols.
llvm-svn: 252588
|
| |
|
|
|
|
|
|
|
|
| |
"Modify internal breakpoints so they resolve just like external
breakpoints do. This allow you to set symbol and file + line internal
breakpoints and have them get updated correctly."
<rdar://problem/16931767>
llvm-svn: 252584
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
triple for a process. He writes, "Changes to the way setting the
triple works on a target so that if the target has passed a fully
specified triple, and the newly passed triple is not a revamp of
the current one, and the current one is fully specified, then do
not replace the existing triple."
Triple handling got a bit more complicated on mac with the addition
of ios/watchos/tvos and their simulators, and tracking the correct
os versions for them so expressions are compiled with the expected
APIs available to the user.
<rdar://problem/19820698>
llvm-svn: 252583
|
| |
|
|
|
|
|
|
|
|
| |
Also, add an async error message if the dyld solib loaded callback function
can't find an ABI (which results in no solibs being loaded in the process).
This is a big error and we should call attention to it.
<rdar://problem/23471384>
llvm-svn: 252581
|
| |
|
|
| |
llvm-svn: 252560
|
| |
|
|
|
|
| |
refactoring with no feature change
llvm-svn: 252553
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Relying on manual Python C API calls is error prone, especially
when trying to maintain compatibility with Python 2 and Python 3.
This patch additionally fixes what appears to be a potentially
serious memory leak, in that were were incref'ing two values
returned from the session dictionary but never decref'ing them.
There was a comment indicating that it was intentional, but the
reasoning was, I believe, faulty and it resulted in a legitimate
memory leak.
Switching everything to PythonObject based classes solves both
the compatibility issues as well as the resource leak issues.
llvm-svn: 252536
|
| |
|
|
|
|
| |
is a slight refactoring that I need as part of a larger master plan. As such, should be NFC
llvm-svn: 252529
|
| |
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
| |
ValueObject itself also gets a say in the process; NFC
llvm-svn: 252516
|
| |
|
|
|
|
|
|
|
|
| |
flags
In this way, when a language needs to tell itself things that are not bound to a type but to a value (imagine a base-class relation, this is not about the type, but about the ValueObject), it can do so in a clean and general fashion
The interpretation of the values of the flags is, of course, up to the language that owns the value (the value object's runtime language, that is)
llvm-svn: 252503
|
| |
|
|
|
|
|
| |
This commit closes the following review:
http://reviews.llvm.org/D14488
llvm-svn: 252498
|
| |
|
|
|
|
| |
I'm primarily testing my git-svn setup.
llvm-svn: 252441
|
| |
|
|
|
|
|
| |
This was breaking but probably missed since it is currently
infrequently used.
llvm-svn: 252438
|
| |
|
|
| |
llvm-svn: 252429
|
| |
|
|
| |
llvm-svn: 252409
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary:
These changes are still incomplete, but we are almost there.
Changes:
- CMake and gmake code
- SWIG code
- minor code additions
Reviewers: emaste, joerg
Subscribers: youri, akat1, brucem, lldb-commits, joerg
Differential Revision: http://reviews.llvm.org/D14042
llvm-svn: 252403
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary:
Since this is within the lldb namespace, the compiler tries to
export a symbol for it. Unfortunately, since it is inlined, the
symbol is hidden and this results in a mess of warnings when
building on OS X with cmake.
Moving it to the lldb_private namespace eliminates that problem.
Reviewers: clayborg
Subscribers: emaste, lldb-commits
Differential Revision: http://reviews.llvm.org/D14417
llvm-svn: 252396
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary:
On Linux, if a thread-specific conditional breakpoint was hit, it
won't necessarily be the thread that hit the breakpoint itself that
evaluates the conditional expression, so the thread that hit the
breakpoint could still be asked to stop, even though it hasn't been
allowed to run since the previous stop.
Reviewers: sivachandra, jingham
Subscribers: lldb-commits
Differential Revision: http://reviews.llvm.org/D14472
llvm-svn: 252391
|
| |
|
|
|
|
|
|
| |
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
|
| |
|
|
| |
llvm-svn: 252384
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Python has a complicated mechanism of checking an objects truthity.
This involves a number of steps, which end with calling two private
methods on an object (if they are implemented). In Python 2 these
two methods are `__nonzero__` and `__len__`, and in Python 3 they
are `__bool__` and `__len__`. Because we *also* define a __len__
method for certain iterable types, this was triggering a situation
in Python 3 where `__nonzero__` wasn't defined, so it was calling
`__len__`, which was returning 0 (for example an SBDebugger with
no targets), and as a result the truthosity was determined to be
False.
We fix this by correctly using ` __bool__` for Python 3, and leave
the behavior under Python 2 unchanged.
Note that this fix is only implemented in the SWIG generation
python script, and not the SWIG generation shell script. Someone
more familiar than me with shell scripts will need to fix them
to support this for Python 3 if desired.
llvm-svn: 252382
|
| |
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
| |
Remove implicit ilist iterator conversions before reapplying r252372
(which will disallow them).
llvm-svn: 252378
|
| |
|
|
|
|
|
|
|
|
|
| |
Fixed Clang-tidy warnings:
* modernize-use-override;
* modernize-use-nullptr;
* modernize-use-default;
* readability-simplify-boolean-expr.
llvm-svn: 252374
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
| |
a thread while
running, don't request the thread status when deciding why we stopped.
llvm-svn: 252355
|
| |
|
|
| |
llvm-svn: 252354
|