| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary:
I came across this while trying to understand what Log::Debug does. It turns out
it does not do anything, as there is no instance of someone setting a debug flag
on a stream. The same is true for the Verbose and AddPrefix flags. Removing
these will enable some cleanups in the Logging class, and it brings us closer
towards the long term goal of standardizing on llvm stream classes.
I have removed these flags and all code the code which tested for their
presence -- there wasn't much of it, mostly in SymbolFileDWARF, which is
probably going away at some point anyway.
The eBinary flag still has some users, so I am letting it life for the time
being.
Reviewers: clayborg, zturner
Subscribers: aprantl, beanz, lldb-commits
Differential Revision: https://reviews.llvm.org/D28616
llvm-svn: 291895
|
| |
|
|
|
|
|
| |
This commit fixes a typo in ABISysV_arm64.cpp.
Log was reporting a call to ABISysV_x86_64::PrepareTrivialCall.
llvm-svn: 291889
|
| |
|
|
|
|
| |
The framework build was constructing the path to LLDBWrapPython incorrectly. It is apparently always in the scripts directory.
llvm-svn: 291788
|
| |
|
|
|
|
| |
I have accidentally added extra llvm:: namespace qualification.
llvm-svn: 291763
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary:
The formatter supports the same options as the string-like classes, i.e. the
ability to truncate the displayed string. I don't anticipate it would be much
used, but it seems consistent.
Reviewers: zturner, clayborg
Subscribers: mgorny, lldb-commits
Differential Revision: https://reviews.llvm.org/D28519
llvm-svn: 291759
|
| |
|
|
| |
llvm-svn: 291756
|
| |
|
|
| |
llvm-svn: 291738
|
| |
|
|
|
|
|
| |
I have previously enabled this test for this configuration. However, it turns
out it only passes for gcc-4.9.
llvm-svn: 291563
|
| |
|
|
|
|
|
|
|
|
| |
Previously it failed to handle nested types inside templated classes
making it impossible to look up these types using the fully qualified
name.
Differential revision: https://reviews.llvm.org/D28466
llvm-svn: 291559
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The llvm_config hack for lldb-server is only necessary for !DYLIB builds, as
otherwise we would get unresolved symbols from lldb libraries which do not track
their dependencies correctly (all of them). In a DYLIB build, the so will
already be added to the link dependencies and we can use that to resolve all
missing symbols.
The proper fix for this would be to have each lldb library track its
dependencies correctly.
llvm-svn: 291555
|
| |
|
|
|
|
|
|
|
|
| |
Reviewers: labath, clayborg
Subscribers: jaydeep, bhushan, lldb-commits, slthakur
Differential Revision: https://reviews.llvm.org/D27088
llvm-svn: 291554
|
| |
|
|
| |
llvm-svn: 291553
|
| |
|
|
|
|
|
|
|
|
| |
Reviewers: labath, clayborg
Subscribers: jaydeep, bhushan, lldb-commits, slthakur
Differential Revision: https://reviews.llvm.org/D27088
llvm-svn: 291549
|
| |
|
|
|
|
|
|
| |
We currently limit the length of TSan returned backtraces to 8, which is not necessary (and a bug, most likely). Let's remove this.
Differential Revision: https://reviews.llvm.org/D28035
llvm-svn: 291522
|
| |
|
|
|
|
|
| |
Use the new --cmakedir option to obtain LLVM_CMAKE_PATH straight from
llvm-config instead of reconstructing it locally.
llvm-svn: 291500
|
| |
|
|
| |
llvm-svn: 291350
|
| |
|
|
| |
llvm-svn: 291349
|
| |
|
|
|
|
|
| |
Patch by Vadim Chugunov
Differential Revision: https://reviews.llvm.org/D27476
llvm-svn: 291291
|
| |
|
|
|
|
|
|
|
| |
Aleksey Shlyapnikov found the memory leak I introduced, recommitted the
Clang change with a fix for this.
This reapplies r291200 reverted in r291250
llvm-svn: 291271
|
| |
|
|
|
|
|
|
|
| |
The original Clang change caused a memory leak detected by asan.
Reverting while I investigate.
This reverts commit r291200.
llvm-svn: 291250
|
| |
|
|
| |
llvm-svn: 291234
|
| |
|
|
| |
llvm-svn: 291233
|
| |
|
|
|
|
|
|
|
| |
Older clangs (<=3.6) complain about a redefinition when we try to specialize a
templace function declared with = delete. Instead, I just don't define the
function body, which will trigger a linker error if someone tries to use an
unknown function.
llvm-svn: 291226
|
| |
|
|
|
|
| |
The clang bug is fixed now. This reverts commit r291100.
llvm-svn: 291225
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary:
To implement wide character reading, editline was mixing FILE*-based access with
a Connection-based one (plus it did some selects on the raw FD), which is very
fragile. Here, I replace it with one which uses only a Connection-based reads.
The code is somewhat longer as I had to read characters one by one to detect the
end of the multibyte sequence.
I've verified that international characters still work in lldb command line on
OSX.
Reviewers: clayborg, zturner
Subscribers: lldb-commits
Differential Revision: https://reviews.llvm.org/D28356
llvm-svn: 291220
|
| |
|
|
|
|
|
|
| |
Wasn't sure I could include ErrorHandling.h here, and evidently I wasn't
building this part (must've made the change using sed after getting
tired of fixing each compilation error individually).
llvm-svn: 291204
|
| |
|
|
| |
llvm-svn: 291200
|
| |
|
|
|
|
| |
the same way as the caller
llvm-svn: 291199
|
| |
|
|
|
|
|
|
|
| |
Also found/fixed one bug identified by this warning in
RenderScriptx86ABIFixups.cpp where a string literal was being used in an
effort to provide a name for an instruction/register, but was instead
being passed as the bool 'isVolatile' parameter.
llvm-svn: 291198
|
| |
|
|
|
|
|
| |
My earlier commit today seem to cause a failure on a darwin buildbot.
I am skipping the test while I investigate the failure.
llvm-svn: 291118
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary:
Some of the mi commands implemented in lldb-mi are incomplete/not confirming to the spec.
- `gdb-show` and `gdb-set` doesn't support getting/setting `disassembly-flavor`
- `environment-cd` should also change the working directory for inferior
- debugger CLI output should be printed as console-stream-output record, rather than being dumped directly
to stdout
- `target-select` should provide inner error message in mi response
Related bug report:
- https://llvm.org/bugs/show_bug.cgi?id=28026
- https://llvm.org/bugs/show_bug.cgi?id=28718
- https://llvm.org/bugs/show_bug.cgi?id=30265
Reviewers: ki.stfu, abidh
Subscribers: abidh, ki.stfu, lldb-commits
Tags: #lldb
Differential Revision: https://reviews.llvm.org/D24711
llvm-svn: 291104
|
| |
|
|
|
|
|
| |
We were sending paths with the host path separator, which meant the remote
target did not understand our packets correctly.
llvm-svn: 291103
|
| |
|
|
|
|
|
|
| |
lldbassert(!"foo") -> lldbassert(0 && "foo")
In one case, this actually detected a logic error in the assertion (missing !).
llvm-svn: 291102
|
| |
|
|
|
|
| |
the test fails due to a bug in ToT clang
llvm-svn: 291100
|
| |
|
|
|
|
|
|
|
|
| |
Added an extra field parser to the `RSModuleDescriptor` class enabling us to
check whether the versions of LLVM used to generated the debug symbols match
across the RenderScript compiler frontend (llvm-rs-cc) and backend (bcc); if
they do not, we warn the user that the debugging experience may be suboptimal
as LLVM IR debug information has no compatibility guarantees.
llvm-svn: 290957
|
| |
|
|
|
|
| |
The logic for install rules was wrong for tools included in the framework if the framework build is disabled.
llvm-svn: 290934
|
| |
|
|
|
|
|
|
|
|
| |
lldb-gtest binary that xcode builds for -scheme lldb-gtest; these tests
won't run on macosx systems. Fixes testsuite failures we started
seeing after 290819.
<rdar://problem/29853778>
llvm-svn: 290917
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Previously it parsed /proc/<pid>/maps for every module separately
resulting in a very slow response time. This CL add some caching and
optimizes the implementation to improve the code from O(n*m) to O(n+m)
where n is the number of modules requested and m is the number of
files mapped into memory.
Differential revision: https://reviews.llvm.org/D28233
llvm-svn: 290895
|
| |
|
|
|
|
|
|
|
|
|
|
| |
r290874 enabled the s390x test, which caused the rest of the tests to start
misbehaving. This is because this test switches the selected platform and the
change persists.
This fixes it by explicitly resetting the platform in a similar way to the gcore
tests do. Potentially we should consider re-setting the platform globally
between each test run to better protect tests from each other.
llvm-svn: 290890
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary:
This patch changes and simplifies the way notes are read from Linux Elf cores.
The current implementation copies the bytes from the notes directly over the lldb structure for 64 bit cores and reads field by field for 32 bit cores. Reading the bytes directly only works if the endianess of the core dump and the platform that lldb are running on matches. The case statements for s390x and x86_64 would would only work on big endian systems and little endian systems respectively. That meant that x86_64 generally worked but s390x didn't unless you were on s390x or another big endian platform.
This patch just reads field by field on all platform and updates the field by field version to allow for those fields which are word size instead of fixed size. It should also slightly simplify adding support for a new Linux platform.
This patch also re-enables the s390x test case in TestLinuxCore.py on all non-s390x platforms as it now passes.
Reviewers: uweigand, clayborg
Differential Revision: https://reviews.llvm.org/D27571
llvm-svn: 290874
|
| |
|
|
|
|
|
|
| |
TestNoreturnUnwind fails on arm/aarch32 linux targets.
Bug is already described for x86_64 android targets in llvm.org/pr31192.
llvm-svn: 290821
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Split the PDB tests into DWARF test and actual PDB tests, the latter
requiring DIA SDK. Use the new LLVMConfig.cmake LLVM_ENABLE_DIA_SDK
symbol to enable the PDB tests rather than relying on
llvm/Config/config.h private include file that is not available when
building standalone.
Differential Revision: https://reviews.llvm.org/D26249
llvm-svn: 290819
|
| |
|
|
|
|
| |
children change will update correctly. Previously the variable view would update the children once and not change. If you were stepping through code where the dynamic type of a variable would change the value and its children, or a synthetic type (like say for a std::vector<int>), the variable view wouldn't update. Now it caches the children and uses the process stop ID to tell when the children need to be updated.
llvm-svn: 290688
|
| |
|
|
| |
llvm-svn: 290687
|
| |
|
|
|
|
|
|
|
|
|
| |
This patch fixes use of incorrect `%zi` to format a plain `int`, and using
`%llu` to format a `uint64_t`. The fix is to use the new typesafe
`llvm::Formatv` based API.
Differential Revision: https://reviews.llvm.org/D28028
Subscribers: lldb-commits
llvm-svn: 290359
|
| |
|
|
| |
llvm-svn: 290282
|
| |
|
|
|
|
|
|
| |
This patch adds the last bit of support to get LLVM_DISTRIBUTION_COMPONENTS working with libLLDB when built as a framework.
This patch adds dummy install targets for binaries built into the framework's Resources directory, and makes the framework's install target depend on all the binaries that get installed with the framework.
llvm-svn: 290273
|
| |
|
|
|
|
|
|
|
|
|
| |
We're seeing some very occasional failures in these tests where the
mini-driver dies with a SIGPIPE. We don't use SIGPIPE for anything, and
the main lldb driver program already ignores SIGPIPE, so ignoring it in
the mini-driver is a good way to remove these spurious failures.
<rdar://problem/29740488>
llvm-svn: 290216
|
| |
|
|
| |
llvm-svn: 290197
|
| |
|
|
|
|
| |
This resolves PR 31433.
llvm-svn: 290180
|