| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
|
|
| |
of the symbol itself rather than forcing clients to do
it. This simplifies the logic for the expression
parser a great deal.
<rdar://problem/16935324>
llvm-svn: 209494
|
|
|
|
| |
llvm-svn: 209303
|
|
|
|
| |
llvm-svn: 207945
|
|
|
|
|
|
|
|
|
| |
Add a callback that will allow an expression to be cancelled between the
expression evaluation stages (for the ClangUserExpressions.)
<rdar://problem/16790467>, <rdar://problem/16573440>
llvm-svn: 207944
|
|
|
|
| |
llvm-svn: 207913
|
|
|
|
|
|
|
|
|
|
|
|
| |
values of variables in the Materializer.
The Materializer should not write the variable
back if its new value is the *same* as the old
value, not if the new value is *different*.
<rdar://problem/16712205>
llvm-svn: 207148
|
|
|
|
| |
llvm-svn: 206836
|
|
|
|
|
|
|
|
| |
dbg_value intrinsics appropriately.
<rdar://problem/16504649>
llvm-svn: 205825
|
|
|
|
|
|
|
| |
This is a purely mechanical change explicitly casting any parameters for printf
style conversion. This cleans up the warnings emitted by gcc 4.8 on Linux.
llvm-svn: 205607
|
|
|
|
|
|
|
|
| |
This is a mechanical change addressing the various sign comparison warnings that
are identified by both clang and gcc. This helps cleanup some of the warning
spew that occurs during builds.
llvm-svn: 205390
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
These changes were written by Greg Clayton, Jim Ingham, Jason Molenda.
It builds cleanly against TOT llvm with xcodebuild. I updated the
cmake files by visual inspection but did not try a build. I haven't
built these sources on any non-Mac platforms - I don't think this
patch adds any code that requires darwin, but please let me know if
I missed something.
In debugserver, MachProcess.cpp and MachTask.cpp were renamed to
MachProcess.mm and MachTask.mm as they picked up some new Objective-C
code needed to launch processes when running on iOS.
llvm-svn: 205113
|
|
|
|
|
|
|
|
|
|
|
| |
if they didn't change, just like it does for
registers. This makes life easier for kernel
debugging and any other situation where values
are read-only.
<rdar://problem/16367795>
llvm-svn: 204764
|
|
|
|
|
|
| |
when other cases get added.
llvm-svn: 204751
|
|
|
|
|
|
| |
that call debug-information intrinsics.
llvm-svn: 204750
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
source info:
(lldb) b puts
(lldb) expr -g -i0 -- (int)puts("hello")
First we will stop at the entry point of the expression before it runs, then we can step over a few times and hit the breakpoint in "puts", then we can continue and finishing stepping and fininsh the expression.
Main features:
- New ObjectFileJIT class that can be easily created for JIT functions
- debug info can now be enabled when parsing expressions
- source for any function that is run throught the JIT is now saved in LLDB process specific temp directory and cleaned up on exit
- "expr -g --" allows you to single step through your expression function with source code
<rdar://problem/16382881>
llvm-svn: 204682
|
|
|
|
|
|
| |
No functionnal change.
llvm-svn: 204545
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a mechanical cleanup of unused functions. In the case where the
functions are referenced (in comment form), I've simply commented out the
functions. A second pass to clean that up is warranted.
The functions which are otherwise unused have been removed. Some of these were
introduced in the initial commit and not in use prior to that point!
NFC
llvm-svn: 204310
|
|
|
|
|
|
|
| |
This reverts part of r204112 (Expression: cleanup unused include).
It looks like MCJIT.h is required to force MCJIT to be linked.
llvm-svn: 204170
|
|
|
|
|
|
|
|
| |
The standard JIT has been discarded in favour of MCJIT. USE_STANDARD_JIT is no
longer defined. Furthermore, the execution engine is now built in
IRExecutionUnit. Simply remove inclusion of both JIT headers.
llvm-svn: 204112
|
|
|
|
| |
llvm-svn: 203737
|
|
|
|
|
|
|
|
|
|
|
| |
erroneously completing Objective-C classes sourced
from the Objective-C runtime without checking if
there was an authoritative version in the debug
information.
<rdar://problem/16065049>
llvm-svn: 203600
|
|
|
|
|
|
|
|
| |
User fixes. Also changed our iterations across
global variables and instruction operands to
reflect the new C++11 approach.
llvm-svn: 203599
|
|
|
|
| |
llvm-svn: 203487
|
|
|
|
|
|
|
|
|
|
|
| |
What was use_iterator is now user_iterator. Also switch to range-based
APIs, as in Clang r203365.
(This part of the change was missed in r203463)
Differential Revision: http://llvm-reviews.chandlerc.com/D3030
llvm-svn: 203475
|
|
|
|
|
|
|
| |
What was use_iterator is now user_iterator. Also switch to range-based
APIs, as in Clang r203365.
llvm-svn: 203463
|
|
|
|
| |
llvm-svn: 203217
|
|
|
|
| |
llvm-svn: 203200
|
|
|
|
|
|
|
|
| |
exceed the bounds of the backing memory.
<rdar://problem/16088322>
llvm-svn: 202899
|
|
|
|
| |
llvm-svn: 202740
|
|
|
|
|
|
|
|
| |
style statements that were assuming size_t were 64 bit were changed, and they were also changed to display them as unsigned values as "size_t" isn't signed.
If you print anything with 'size_t', please cast it to "uint64_t" in the printf and use PRIu64 or PRIx64.
llvm-svn: 202738
|
|
|
|
| |
llvm-svn: 202723
|
|
|
|
|
|
|
| |
This seems reasonable and the BackticksWithNoTargetTestCase suggests it
should be this way.
llvm-svn: 202722
|
|
|
|
|
|
| |
<rdar://problem/15949113>
llvm-svn: 202561
|
|
|
|
|
|
|
|
|
|
|
| |
read during materialization. First of all, report
if we can't read the data for some reason. Second,
consult the ValueObject's error and report that if
there's some problem.
<rdar://problem/16074201>
llvm-svn: 202552
|
|
|
|
|
|
| |
match the clang update (r202346) on ASTContext
llvm-svn: 202376
|
|
|
|
|
|
| |
This reverts commit r201671, because the clang changes have been reverted.
llvm-svn: 201759
|
|
|
|
|
|
|
|
|
| |
to a variable. This helps people figure out what
happened if they tried to do something to the variable
and it didn't work because we gave it the default type
of void*.
llvm-svn: 201737
|
|
|
|
|
|
|
| |
Clang now requires calling CompilerInstance::createVirtualFileSystem
before CompilerInstance::createFileManager.
llvm-svn: 201671
|
|
|
|
| |
llvm-svn: 201268
|
|
|
|
|
|
| |
<rdar://problem/15958296>
llvm-svn: 200951
|
|
|
|
|
|
|
|
|
| |
selector when compiling an expression in an
Objective-C context.
<rdar://problem/15797390>
llvm-svn: 200950
|
|
|
|
|
|
|
|
|
|
|
|
| |
The many many benefits include:
1 - Input/Output/Error streams are now handled as real streams not a push style input
2 - auto completion in python embedded interpreter
3 - multi-line input for "script" and "expression" commands now allow you to edit previous/next lines using up and down arrow keys and this makes multi-line input actually a viable thing to use
4 - it is now possible to use curses to drive LLDB (please try the "gui" command)
We will need to deal with and fix any buildbot failures and tests and arise now that input/output and error are correctly hooked up in all cases.
llvm-svn: 200263
|
|
|
|
|
|
| |
we can see exactly what data was put where.
llvm-svn: 199701
|
|
|
|
| |
llvm-svn: 199689
|
|
|
|
|
|
| |
don't know their bit alignment.
llvm-svn: 199173
|
|
|
|
|
|
|
|
| |
As done in other DW_OP_* cases, return an error if the stack is empty
rather than eventually crashing elsewhere. Encountered on big-endian
MIPS, where LLVM bugs currently result in invalid .debug_loc data.
llvm-svn: 199110
|
|
|
|
|
|
|
|
|
| |
materialize a variable in a register correctly
if the variable is a pointer. This fixes a
regression introduced by my commit of Oct. 22nd
(r193191).
llvm-svn: 198718
|
|
|
|
|
|
| |
for making pointer-valued constants.
llvm-svn: 197829
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
of Objective-C classes are completed, and that
variables of Objective-C types have their types
completed when the variables are reported.
This fixes a long-standing issue where ivars did
not show up correctly on 32-bit OS X.
<rdar://problem/12184093>
llvm-svn: 197775
|
|
|
|
|
|
|
|
| |
specify a pointer size until code gen. So we just
make all our pointer-sized integer literals 64-bit.
That doesn't seem to hurt anything.
llvm-svn: 197774
|