| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
|
| |
Addresses pr/21190 (http://llvm.org/bugs/show_bug.cgi?id=21190).
r219169 implemented this change list:
http://reviews.llvm.org/D5472 for more details.
llvm-svn: 219461
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This setting contains the following:
A list containing all the arguments to be passed to the expression parser compiler.
This change also ensures quoted arguments are handled appropriately.
See http://reviews.llvm.org/D5472 for more details.
Change by Tong Shen.
llvm-svn: 219169
|
|
|
|
|
|
|
|
|
|
|
|
| |
more accessible from
the user level. It adds the ability to invent new stepping modes implemented by python classes,
and to view the current thread plan stack and to some extent alter it.
I haven't gotten to documentation or tests yet. But this should not cause any behavior changes
if you don't use it, so its safe to check it in now and work on it incrementally.
llvm-svn: 218642
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Those wrapper functions seems not used by lldb... Removed
Reference for
replacing JITMemoryManager with SectionMemoryManager
replacing "llvm::JITMemoryManager::CreateDefaultMemManager()" with "new llvm::SectionMemoryManager()"
http://llvm.org/viewvc/llvm-project/llvm/trunk/tools/llvm-jitlistener/llvm-jitlistener.cpp?r1=218316&r2=218315&pathrev=218316
Change by Tong Shen.
Tested:
Ubuntu 14.04 x86_64
MacOSX 10.9.5 with Xcode Version 6.1 (6A1030) (Beta)
llvm-svn: 218383
|
|
|
|
| |
llvm-svn: 217862
|
|
|
|
|
|
|
| |
as part of an attempt to get lldb building inside llvm with -Werror
enabled.
llvm-svn: 217418
|
|
|
|
| |
llvm-svn: 217003
|
|
|
|
|
|
|
| |
way ownership of memory buffers is handled in
clang's SourceManager.
llvm-svn: 216810
|
|
|
|
| |
llvm-svn: 216603
|
|
|
|
|
|
|
|
| |
install a crash handler.
<rdar://problem/18083226>
llvm-svn: 216309
|
|
|
|
| |
llvm-svn: 216247
|
|
|
|
|
|
|
|
| |
This continues the effort to get Host code moved over to HostInfo,
and removes many more instances of preprocessor defines along the
way.
llvm-svn: 216195
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch creates a HostInfo class, a static class used to answer
basic queries about the host platform. As part of this change,
some functionality is moved from Host to HostInfo, and relevant
fixups are performed in the rest of the codebase.
This is part of a larger effort to isolate more code in the Host
layer into platform-specific groups, to make it easier to make
platform specific changes for a particular Host without breaking
other hosts.
Reviewed by: Greg Clayton
Differential Revision: http://reviews.llvm.org/D4963
llvm-svn: 215992
|
|
|
|
| |
llvm-svn: 215969
|
|
|
|
| |
llvm-svn: 215681
|
|
|
|
|
|
| |
udata/sdata forms. By Greg Clayton
llvm-svn: 215379
|
|
|
|
|
|
|
|
| |
* transfered => transferred
* unkown => unknown
* sucessfully => successfully
llvm-svn: 215367
|
|
|
|
|
|
|
| |
jit was re-added back to LLVM, so now we require to link against it
again. Should it get removed again, then revert this revert.
llvm-svn: 215170
|
|
|
|
| |
llvm-svn: 215119
|
|
|
|
| |
llvm-svn: 215107
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
DW_OP_fbreg(N) DW_OP_piece(4) DW_OP_fbreg(M) DW_OP_piece(8)
DW_OP_fbreg(N) DW_OP_piece(4) DW_OP_piece(8)
The first grabs 4 bytes from FP+N followed by 8 bytes from FP+M, the second grabs 4 bytes from FP+N followed by zero filling 8 bytes which are unavailable. Of course regiters are stuff supported:
DW_OP_reg3 DW_OP_piece(4) DW_OP_reg8 DW_OP_piece(8)
The fix does the following:
1 - don't push the full piece value onto the stack, keep it on the side
2 - fill zeros for DW_OP_piece(N) opcodes that have nothing on the stack (instead of previously consuming the full piece that was pushed onto the stack)
3 - simplify the logic
<rdar://problem/16930524>
llvm-svn: 214415
|
|
|
|
| |
llvm-svn: 214327
|
|
|
|
| |
llvm-svn: 214323
|
|
|
|
| |
llvm-svn: 214319
|
|
|
|
|
|
|
| |
__INT?_TYPE__ is now explicitly, so adding an explicit 'signed'
specifier causes errors.
llvm-svn: 214233
|
|
|
|
|
|
|
|
|
|
|
| |
See the following llvm change for details:
r213743 | tnorthover | 2014-07-23 05:32:47 -0700 (Wed, 23 Jul 2014) | 9 lines
AArch64: remove arm64 triple enumerator.
This change fixes build breaks on Linux and MacOSX lldb.
llvm-svn: 213755
|
|
|
|
|
|
|
|
| |
result variable and use in in "Process::LoadImage" so that,
for instance, "process load" doesn't increment the return
variable number.
llvm-svn: 213440
|
|
|
|
|
|
|
|
|
|
| |
to be able to piece together a value that is spread across multiple registers.
Patch from Adrian Prantl.
<rdar://problem/16040521>
llvm-svn: 212867
|
|
|
|
| |
llvm-svn: 212791
|
|
|
|
|
|
|
|
|
|
|
| |
Fixes include:
- Don't say that "<arch>-apple-ios" is compatible with "<arch>-apple-macosx"
- Fixed DynamicLoaderMacOSXDYLD so specify an architecture that was converted solely from a cputype and subtype, just specify the file + UUID.
- Fixed PlatformiOSSimulator::GetSupportedArchitectureAtIndex() so it returns the correct archs
- Fixed SymbolFileDWARFDebugMap to load .o files correctly by just specifying the architecture without the vendor and OS now that "<arch>-apple-ios" is not compatible with "<arch>-apple-macosx" so we can load .o files correctly for DWARF with debug map
- Fixed the coded in TargetList::CreateTarget() so it does the right thing with an underspecified triple where just the arch is specified.
llvm-svn: 212783
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The current strategy for host allocation is to choose a random
address and attempt to allocate there, eventually failing if the
allocation cannot be satisfied.
The C standard only guarantees that RAND_MAX >= 32767, so for
platforms that use a very small RAND_MAX allocations will fail
with very high probability. On such platforms (Windows is one),
you can reproduce this trivially by running lldb, typing "expr (3)"
and then hitting enter you see a failure. Failures generally
happen with a frequency of about 1 failure every 5 evaluations.
There is no good reason that allocations need to look like "real"
pointers, so this patch changes the allocation scheme to simply
jump straight to the end and grab a free chunk of memory.
Reviewed By: Sean Callanan
Differential Revision: http://reviews.llvm.org/D4300
llvm-svn: 212630
|
|
|
|
| |
llvm-svn: 212582
|
|
|
|
|
|
|
| |
when you continue to finish off the function call, the expression result
will be included as part of the thread stop info.
llvm-svn: 212506
|
|
|
|
| |
llvm-svn: 212411
|
|
|
|
| |
llvm-svn: 212410
|
|
|
|
| |
llvm-svn: 212391
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
off_t is a type which is used for file offsets. Even more
specifically, it is only used by a limited number of C APIs that
deal with files. Any usage of off_t where the variable is not
intended to be used with one of these APIs is a bug, by definition.
This patch corrects some easy mis-uses of off_t, generally by
converting them to lldb::offset_t, but sometimes by using other
types such as size_t, when appropriate.
The use of off_t to represent these offsets has worked fine in
practice on linux-y platforms, since we used _FILE_OFFSET_64 to
guarantee that off_t was a uint64. On Windows, however,
_FILE_OFFSET_64 is unrecognized, and off_t will always be 32-bit.
So the usage of off_t on Windows actually leads to legitimate bugs.
Reviewed by: Greg Clayton
Differential Revision: http://reviews.llvm.org/D4358
llvm-svn: 212192
|
|
|
|
| |
llvm-svn: 212172
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change brings in lldb-gdbserver (llgs) specifically for Linux x86_64.
(More architectures coming soon).
Not every debugserver option is covered yet. Currently
the lldb-gdbserver command line can start unattached,
start attached to a pid (process-name attach not supported yet),
or accept lldb attaching and launching a process or connecting
by process id.
The history of this large change can be found here:
https://github.com/tfiala/lldb/tree/dev-tfiala-native-protocol-linux-x86_64
Until mid/late April, I was not sharing the work and continued
to rebase it off of head (developed via id tfiala@google.com). I switched over to
user todd.fiala@gmail.com in the middle, and once I went to github, I did
merges rather than rebasing so I could share with others.
llvm-svn: 212069
|
|
|
|
|
|
|
|
| |
Reviewed by: Sean Callanan
Differential Revision: http://reviews.llvm.org/D4282
llvm-svn: 211968
|
|
|
|
| |
llvm-svn: 211728
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, only the starting locations of the candidate interval
and the existing interval were compared. To correctly detect
range intersections, it is necessary to compare the entire range
of both intervals against each other.
Reviewed by: scallanan
Differential Revision: http://reviews.llvm.org/D4286
llvm-svn: 211726
|
|
|
|
|
|
| |
The patch is as is with the functionality left disabled for apple vendors because of performance regressions. If this is enabled it ends up searching for symbols in all shared libraries that are loadeded.
llvm-svn: 211638
|
|
|
|
|
|
|
|
| |
simulator).
<rdar://problem/17399406>
llvm-svn: 211536
|
|
|
|
|
|
| |
Caught by the clang static analyzer by Jason Molenda.
llvm-svn: 210941
|
|
|
|
|
|
|
|
| |
Address the 'variable set but not used' warning from GCC. In some cases a few
additional calls were removed where there should be no visible side effects of
the calls (i.e. should not effect any cached state).
llvm-svn: 210879
|
|
|
|
| |
llvm-svn: 210765
|
|
|
|
| |
llvm-svn: 209809
|
|
|
|
| |
llvm-svn: 209807
|
|
|
|
| |
llvm-svn: 209703
|