| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Use of --rerun-all-issues will enable any test method failure, not just
test methods marked with the flakey decorator, to rerun.
Currently this does not change the flakey logic's immediate rerun
attempt. I want to make sure this doesn't cause any significant issues
before changing that part.
The rerun reporting is only known to work properly with the
default (new) BasicResultsFormatter reporting. Once we work out
any issues, I'll go back and make sure the curses output handles
it properly as well.
llvm-svn: 255543
|
|
|
|
| |
llvm-svn: 255542
|
|
|
|
|
|
|
| |
Reviewed By: Tamas Berghammer, Pavel Labath
Differential Revision: http://reviews.llvm.org/D15428
llvm-svn: 255525
|
|
|
|
|
|
| |
Differential revision: http://reviews.llvm.org/D15355
llvm-svn: 255499
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary:
Previously the add_test_categories would simply overwrite the current set of categories for a
method. This change makes the decorator truly "add" categories, by extending the current set of
categories instead of replacing it.
To do this, I have:
- replaced the getCategories() property on a method (which was itself a method), with a simple
list property "categories". This makes add_test_categories easier to implement, and test
categories isn't something which should change between calls anyway.
- rewritten the getCategoriesForTest function to merge method categories with the categories of
the test case. Previously, it would just use the method categories if they were present. I have
also greatly simplified this method. Originally, it would use a lot of introspection to enable
it being called on various types of objects. Based on my tests, it was only ever being called
on a test case. The new function uses much less introspection then the preivous one, so we
should easily catch any stray uses, if there are any, as they will generate exceptions now.
Reviewers: zturner, tfiala, tberghammer
Subscribers: lldb-commits
Differential Revision: http://reviews.llvm.org/D15451
llvm-svn: 255493
|
|
|
|
|
|
| |
one of the tests seems to (occasionally) fail with clang as well.
llvm-svn: 255492
|
|
|
|
| |
llvm-svn: 255490
|
|
|
|
|
|
|
|
|
|
| |
sequences are yet to be supported in LLDB
Reviewers: jaydeep.
Subscribers: lldb-commits.
Differential Revision: http://reviews.llvm.org/D15488
llvm-svn: 255488
|
|
|
|
|
|
|
| |
Missed commit in r255439.
Differential Revision: http://reviews.llvm.org/D15312
llvm-svn: 255440
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When multiple functions are found by name, lldb removes duplicate entries of
functions with the same type, so the first function in the symbol context list
is chosen, even if it isn't in scope. This patch uses the declaration context
of the execution context to select the function which is in scope.
This fixes cases like the following:
int func();
namespace ns {
int func();
void here() {
// Run to BP here and eval 'p func()';
// lldb used to find ::func(), now finds ns::func().
}
}
Reviewed by: clayborg
Subscribers: lldb-commits
Differential Revision: http://reviews.llvm.org/D15312
llvm-svn: 255439
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Also adds full path info for exceptional exits and timeouts when
no test method is currently running.
Adds --rerun-all-issues command line arg. If specified, all
test issues are eligible for rerun. If not specified, only tests
marked flakey are eligible for rerun.
The actual rerunning will occur in an upcoming change. This
change just handles tha accounting of what should be rerun.
llvm-svn: 255438
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
stl upper_bound method instead of lower_bound - we were
failing to find some cached data in the L1 cache resulting
in extra memory read packets while stepping.
The bug with the existing code looked like this:
If the L1 cache has 8 bytes at address 0x1000 and 8 bytes
at address 0x2000 and we are searching for 4 bytes at 0x2004,
the use of lower_bound would return the end() of the container
and so we would incorrectly treat the memory as uncached.
(the L1 cache is memory seeded from debugserver in the T aka
questionmark packet, where debugserver will send up the stack
memory that likely contains the caller's stack pointer and
frame pointer values.)
<rdar://problem/23869227>
llvm-svn: 255421
|
|
|
|
| |
llvm-svn: 255419
|
|
|
|
|
|
|
|
|
| |
include two stack frames worth of unwind information instead of
just one -- the unwinder is trying to fetch two stack frames in
more instances now and we're sending extra memory reads resulting
in a performance degredation while stepping.
llvm-svn: 255417
|
|
|
|
| |
llvm-svn: 255400
|
|
|
|
| |
llvm-svn: 255385
|
|
|
|
|
|
| |
This reverts commit f994b46a2028c8a8b9b55fe010a95122bca07540.
llvm-svn: 255381
|
|
|
|
|
|
| |
Differential Revision: http://reviews.llvm.org/D15435
llvm-svn: 255379
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary: The Hexagon ABI plugin uses hardcoded registers when setting up function calls. This is OK for the Hexagon simulator, but the register numbers are different on the gdbserver running on hardware. Change the hardcoded registers to LLDB generic registers.
Reviewers: clayborg
Subscribers: lldb-commits
Differential Revision: http://reviews.llvm.org/D15457
llvm-svn: 255374
|
|
|
|
|
|
|
|
| |
warnings in source/Target/Target.cpp.
Simplify smart pointers checks in conditions.
llvm-svn: 255364
|
|
|
|
| |
llvm-svn: 255363
|
|
|
|
| |
llvm-svn: 255361
|
|
|
|
| |
llvm-svn: 255360
|
|
|
|
|
|
|
| |
and appends them to our list of comments (which can additionally include
things like decoded addresses).
llvm-svn: 255358
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
marked flakey.
This will be used in a future change to support rerunning flakey tests
that hit a test result isue in a low-load, single worker test runner phase.
This is implemented as an additive-style event rather than being
evaluated and added to the start_test event because the decorator code
only runs after the start_test event is created and sent. i.e.
LLDBTestResult.startTest() runs before the test method decorators run.
llvm-svn: 255351
|
|
|
|
|
|
|
|
|
|
| |
LLDB don't detect the loading of a shared object file linked against the
main executable before the static initializers are executed for the
given module. Because of this it is not possible to get breakpoint hits
in these static initializers and to display proper debug info in case of
a crash in these codes.
llvm-svn: 255342
|
|
|
|
| |
llvm-svn: 255341
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary: If six.py is simlink'd, an installation won't be able to find it unless it has access to the source tree that lldb was built from.
Reviewers: zturner
Subscribers: lldb-commits
Differential Revision: http://reviews.llvm.org/D15422
llvm-svn: 255340
|
|
|
|
|
|
|
| |
Adds support for reading a maximum of six integer arguments from a renderscript hook on X86_64.
Author: Luke Drummond <luke.drummond@codeplay.com>
llvm-svn: 255338
|
|
|
|
|
|
|
| |
The new test summary formatter does not honor the "expected timeout" markings, which makes our
buildbots all red. I'm switching it off by default until we figure out a way to make this work.
llvm-svn: 255335
|
|
|
|
|
|
|
| |
And, turns off verbose mode by default. This must have been switched
on as the default when somebody was testing.
llvm-svn: 255310
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary: NetBSD is like FreeBSD and Linux in these routines.
Reviewers: clay.chang, tfiala, emaste, joerg
Subscribers: lldb-commits, emaste
Differential Revision: http://reviews.llvm.org/D15374
llvm-svn: 255308
|
|
|
|
| |
llvm-svn: 255280
|
|
|
|
| |
llvm-svn: 255279
|
|
|
|
| |
llvm-svn: 255278
|
|
|
|
| |
llvm-svn: 255277
|
|
|
|
| |
llvm-svn: 255276
|
|
|
|
| |
llvm-svn: 255275
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary: When the Hexagon ABI was added, it was inadvertently left out of initialization/termination. This patch adds it.
Reviewers: clayborg
Subscribers: lldb-commits
Differential Revision: http://reviews.llvm.org/D15347
llvm-svn: 255268
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Adding the modules to the global module list eleminate issues in the
case when a module is unloaded from the target but some object (e.g.
breakpoint) still referencing them with weak pointers. It also speeds
up the case when we load, unload, load the same shared library because
the global module cache will keep the parsed debug info around between
the 2 load (this scenario happens for some code on android).
Differential revision: http://reviews.llvm.org/D15415
llvm-svn: 255260
|
|
|
|
|
|
|
|
|
|
|
|
| |
These architectures already using the gold linker for the android
framework and switching to gold gives us the opportunity to enable ICF.
Safe ICF (identical code folding) reduces the size of an optimized and
striped binary by ~5%.
Differential revision: http://reviews.llvm.org/D15379
llvm-svn: 255240
|
|
|
|
|
|
|
| |
Patch creates a member function that decides when to JIT all the details about an allocation.
By checking for zero pointers we can avoid the situation where we store uninitialised data from previously inspecting the allocation during creation.
llvm-svn: 255238
|
|
|
|
| |
llvm-svn: 255237
|
|
|
|
|
|
|
| |
Also adds enable.py/disable.py script to simplify turning on and off
the issue_verification tests helpful for testing a results formatter.
llvm-svn: 255161
|
|
|
|
| |
llvm-svn: 255159
|
|
|
|
|
|
|
|
| |
This was an option to display a graphical progress bar. Nobody
is using this, and it doesn't work correctly anyway with the new
result formatter.
llvm-svn: 255153
|
|
|
|
|
|
|
| |
This removes the option to not print some one time version and
diagnostic information when running the test suite.
llvm-svn: 255152
|
|
|
|
|
|
|
| |
This is part of a larger effort to remove unused command line
options from dotest.py.
llvm-svn: 255151
|
|
|
|
|
|
|
|
| |
This removes the failfast command line option as part of an effort
to simplify dotest and remove unused command line options. You can
still Ctrl+C any time you want to exit early.
llvm-svn: 255150
|
|
|
|
|
|
| |
This is part of an effort to remove unused command line options.
llvm-svn: 255143
|