| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
| |
Differential Revision: https://mail.google.com/mail/u/0/?zx=w4areffgjbgg#inbox/151cb6afe6169bb0
llvm-svn: 256283
|
|
|
|
|
|
|
|
|
| |
It has an existing XFAIL annotation for GCC >= 4.9 but it also fails on
FreeBSD 10.x with Clang 3.4.1.
llvm.org/pr25925
llvm-svn: 256270
|
|
|
|
|
|
| |
This new failure has been noted in the existing PR, llvm.org/pr15824
llvm-svn: 256268
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is generating a SIGSEGV somewhere around 1 in 10 runs on OS X.
Skip the whole test to avoid testbot noise until we can get the
SIGSEGV addressed.
Tracking with:
https://llvm.org/bugs/show_bug.cgi?id=25924
llvm-svn: 256257
|
|
|
|
|
|
|
| |
Fixes:
https://llvm.org/bugs/show_bug.cgi?id=25922
llvm-svn: 256255
|
|
|
|
|
|
|
|
|
|
| |
arguments.
Bug: https://llvm.org/bugs/show_bug.cgi?id=25847
It now gives a more specific error message and then returns instead of trying to select the wrong frame.
llvm-svn: 256251
|
|
|
|
|
|
| |
llvm.org/pr25819
llvm-svn: 256250
|
|
|
|
|
|
| |
It was a copy-and-paste leftover.
llvm-svn: 256248
|
|
|
|
|
|
|
|
|
| |
None of the documentation mentions that the entries are packed structs
and also none of the other implementation I found pack them.
Differential revision: http://reviews.llvm.org/D15715
llvm-svn: 256244
|
|
|
|
| |
llvm-svn: 256223
|
|
|
|
| |
llvm-svn: 256212
|
|
|
|
| |
llvm-svn: 256147
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary: Also xfailed for GCC as there is an problem with debug info generation.
Reviewers: granata.enrico
Subscribers: lldb-commits
Differential Revision: http://reviews.llvm.org/D15657
llvm-svn: 256067
|
|
|
|
|
|
| |
That was not meant to go in, as it was for testing my last change.
llvm-svn: 256062
|
|
|
|
|
|
|
| |
Some of the Green Dragon tests were failing because they didn't
have a TERM set.
llvm-svn: 256059
|
|
|
|
| |
llvm-svn: 256053
|
|
|
|
|
|
|
|
| |
This allows LLDB to deal correctly with expression result variables declared via the C++11 'auto' keyword
rdar://problem/23960490
llvm-svn: 256051
|
|
|
|
|
|
| |
lldb-python-testsuite shared schemes used by Xcode buildbot
llvm-svn: 256043
|
|
|
|
|
|
| |
names that this formatter uses for fields; use the {} syntax to make it so that a failure to parse the summary doesn't cause the entire printout to fail
llvm-svn: 256042
|
|
|
|
| |
llvm-svn: 256034
|
|
|
|
| |
llvm-svn: 256033
|
|
|
|
|
|
|
| |
The llvm.org Green Dragon OS X lldb builder will be using this
target to run the LLDB Python test suite.
llvm-svn: 256027
|
|
|
|
|
|
|
| |
tracking bug:
https://llvm.org/bugs/show_bug.cgi?id=25872
llvm-svn: 256006
|
|
|
|
|
|
|
| |
The incorrect instruction emulation caused issues in the stack unwinding
code when strd was used to push 2 register to the stack with writeback.
llvm-svn: 256000
|
|
|
|
| |
llvm-svn: 255973
|
|
|
|
|
|
|
|
|
|
|
| |
resolver. Also
have the breakpoint description print the precondition description if one exists.
No behavior change.
<rdar://problem/22885189>
llvm-svn: 255972
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
"thread-pcs" key is added to the T (questionmark) packet in
gdb-remote protocol so that lldb doesn't need to query the
pc values of every thread before it resumes a process.
The only odd part with this is that I'm sending the pc
values in big endian order, so we need to know the endianness
of the remote process before we can use them. All other
register values in gdb-remote protocol are sent in native-endian
format so this requirement doesn't exist. This addition is a
performance enhancement -- lldb will fall back to querying the
pc of each thread individually if it needs to -- so when
we don't have the byte order for the process yet, we don't
use these values. Practically speaking, the only way I've
been able to elicit this condition is for the first
T packet when we attach to a process.
<rdar://problem/21963031>
llvm-svn: 255942
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
--rerun-all-issues"
and
Revert "prevent rerun logic from kicking in on test runs including aarch64."
This reverts commits:
r255719
r255747
llvm-svn: 255935
|
|
|
|
|
|
|
| |
Some of the newer structures were not protected. Now that we have
a recursive lock, we just lock the whole handle_event() call.
llvm-svn: 255917
|
|
|
|
|
|
|
|
| |
Currently we can just inspect the details of the most common allocation types.
This patch allows us to support all the types defined by the RS runtime in its `RsDataType` enum.
Including handlers, matrices and packed graphical data.
llvm-svn: 255904
|
|
|
|
|
|
|
|
|
|
| |
Some distributions of python have their version defined as follows in patchlevel.h (note the '+'):
#define PY_VERSION "2.7.9+"
The '+' char needs to be stripped by the cmake regex so that LLDBs python lib detection is successful.
Differential Revision: http://reviews.llvm.org/D15566
llvm-svn: 255893
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch adds support for printing global static const variables which are given a DW_AT_const_value DWARF tag by clang.
Fix for bug https://llvm.org/bugs/show_bug.cgi?id=25653
Reviewers: clayborg, tberghammer
Subscribers: emaste, lldb-commits
Differential Revision: http://reviews.llvm.org/D15576
llvm-svn: 255887
|
|
|
|
| |
llvm-svn: 255885
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary:
As we override the indent option of the LLVM style, we need to override the access modifier
offset as well. Otherwise, classes will be formatted like such
class A
{
public:
int foo;
};
which is not used anywhere in LLDB. This option makes clang-format style more similar to LLDB and
brings it closer to the original intention of LLVM style, which was to not indent access
modifiers.
Reviewers: zturner, tfiala
Subscribers: lldb-commits
Differential Revision: http://reviews.llvm.org/D15562
llvm-svn: 255882
|
|
|
|
|
|
|
|
|
|
|
| |
We've now seen the rerun test phase hang in a few
scenarios. Eliminate the serial test runner (which
is not exercised nearly as much as the others), by
using a multi-worker test runner strategy with a single
worker. This should rule out whether this is related
to the serial test runner strategy.
llvm-svn: 255880
|
|
|
|
|
|
| |
Demangling complex Boost symbols can exhaust the default stack size. In practice, any thread that calls into LLDB functionality that touches symbols runs this risk. Guaranteeing a reasonable minimum for our own private state thread addressees some known scenarios debugging processes that make use of cpp-netlib.
llvm-svn: 255868
|
|
|
|
|
|
| |
Only demangle if this isn't the the value for the "preference" argument indicating the user wants the demangled name. This will stop a lot of symbols from being demangled when parsing the symbol table in ObjectFileMachO.
llvm-svn: 255864
|
|
|
|
| |
llvm-svn: 255863
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch reworks the breakpoint filter-by-language patch to use the
symbol context instead of trying to guess the language solely from the
symbol's name. This has the advantage that symbols compiled with debug
info will have their actual language known. Symbols without debug info
will still do the same "guess"ing because Symbol::GetLanguage() is
implemented using Mangled::GuessLanguage(). The recognition of ObjC
names was merged into Mangled::GuessLanguage.
Reviewed by: jingham, clayborg
Subscribers: lldb-commits
Differential Revision: http://reviews.llvm.org/D15326
llvm-svn: 255808
|
|
|
|
|
|
|
| |
I added these long ago, but as we work to simplify the Xcode
project, their lack of use has made them cleanup targets.
llvm-svn: 255775
|
|
|
|
| |
llvm-svn: 255774
|
|
|
|
| |
llvm-svn: 255771
|
|
|
|
|
|
|
|
|
|
|
| |
igor is a tool to detect common problems and style conformance issues in
man pages and other documents. This is a non-content change to address
the items it reported, before making content changes.
See http://www.wonkity.com/~wblock/igor/igor.1.html for more information
about igor(1).
llvm-svn: 255769
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary:
This adds ability to mark test that do not complete due to hangs, crashes, etc., as "expected",
to avoid flagging the build red for a known problem. Functionally, this extends the scope of the
existing expectedFailureXXX decorators to cover these states as well. Once this is in, I will
start replacing the magic list of failing tests in dosep.py with our regular annotations which
should hopefully make code simpler.
Reviewers: tfiala
Subscribers: lldb-commits
Differential Revision: http://reviews.llvm.org/D15530
llvm-svn: 255763
|
|
|
|
|
|
|
| |
Workaround part 2 for:
https://llvm.org/bugs/show_bug.cgi?id=25844
llvm-svn: 255747
|
|
|
|
|
|
| |
Fixes target membership settings from my last check-in.
llvm-svn: 255746
|
|
|
|
| |
llvm-svn: 255742
|
|
|
|
|
|
|
|
|
|
| |
located - path that contains the test cases - and teach the test suite driver to resolve paths that contain symbolic links to test cases
This is meant to reduce the typing that one needs to do to get from the test subdirectory to actual test cases. Now one can just do
$ ./dotest.py ./testcases/<yaddayaddayadda>
llvm-svn: 255741
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary:
DWARF 5 proposes a reinvented .debug_macro section. This change follows
that spec.
Currently, only GCC produces the .debug_macro section and hence
the added test is annottated with expectedFailureClang.
Reviewers: spyffe, clayborg, tberghammer
Subscribers: lldb-commits
Differential Revision: http://reviews.llvm.org/D15437
llvm-svn: 255729
|
|
|
|
|
|
|
| |
This is a workaround for:
llvm.org/pr25844
llvm-svn: 255719
|