| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch adds support the command 'source info' as follows:
(lldb) help source info
Display source line information (as specified) based on the current executable's
debug info.
Syntax: source info <cmd-options>
Command Options Usage:
source info [-c <count>] [-s <shlib-name>] [-f <filename>] [-l <linenum>] [-e <linenum>]
source info [-c <count>] [-s <shlib-name>] [-n <symbol>]
source info [-c <count>] [-a <address-expression>]
-a <address-expression> ( --address <address-expression> )
Lookup the address and display the source information for the corresponding
file and line.
-c <count> ( --count <count> )
The number of line entries to display.
-e <linenum> ( --end-line <linenum> )
The line number at which to stop displaying lines.
-f <filename> ( --file <filename> )
The file from which to display source.
-l <linenum> ( --line <linenum> )
The line number at which to start the displaying lines.
-n <symbol> ( --name <symbol> )
The name of a function whose source to display.
-s <shlib-name> ( --shlib <shlib-name> )
Look up the source in the given module or shared library (can be specified
more than once).
For example:
(lldb) source info --file x.h
Lines for file x.h in compilation unit x.cpp in `x
[0x0000000100000d00-0x0000000100000d10): /Users/dawn/tmp/./x.h:10
[0x0000000100000d10-0x0000000100000d1b): /Users/dawn/tmp/./x.h:10
The new options are used to fix the MI command:
-symbol-list-lines <file>
which didn't work for header files because it called:
target modules dump line-table <file>
which only dumps line tables for a compilation unit.
The patch also fixes a bug in the error reporting when no files were supplied to the command. Previously you'd get:
(lldb) target modules dump line-table
error:
Syntax:
error: no source filenames matched any command arguments
Now you get:
error: file option must be specified.
Reviewed by: clayborg, jingham, ki.stfu
Subscribers: lldb-commits
Differential Revision: http://reviews.llvm.org/D15593
llvm-svn: 256863
|
|
|
|
| |
llvm-svn: 256851
|
|
|
|
|
|
| |
Test fails in about 1% of buildbot runs. Marking as flaky to avoid the noise.
llvm-svn: 256835
|
|
|
|
|
|
|
| |
I'm getting rid of the expected timeouts. I'll XFAIL/skip any tests that show up as failing after
this (I haven't seen any when running locally, but maybe the buildbot will disagree).
llvm-svn: 256827
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary:
This removes the old logic for rerunning flaky tests. The new test runners will take care of
rerunning failing tests.
Reviewers: tfiala
Subscribers: lldb-commits
Differential Revision: http://reviews.llvm.org/D15855
llvm-svn: 256824
|
|
|
|
|
|
|
| |
I suspect the test was hanging due to the attach deadlock. This was fixed and the test has passed
last 200 buildbot runs.
llvm-svn: 256755
|
|
|
|
|
|
| |
The whole test is skipped already, so it's not running anyway.
llvm-svn: 256752
|
|
|
|
|
|
|
| |
I think it was timing out because of the attach deadlocks, which are now fixed. In any case, it
has passed last 200 buildbot runs, so I am enabling it.
llvm-svn: 256748
|
|
|
|
|
|
|
| |
The test has passed last 200 buildbot runs, so it's hopefully working now. I'll watch buildbots
for signs of trouble.
llvm-svn: 256746
|
|
|
|
|
|
|
| |
I believe the cause for this was the attach lockup fixed in r246756. I will enable this tests and
observe the buildbots for signs of problems.
llvm-svn: 256744
|
|
|
|
|
|
| |
The test in question was removed in r249613.
llvm-svn: 256741
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
This allows LLDB to deal correctly with expression result variables declared via the C++11 'auto' keyword
rdar://problem/23960490
llvm-svn: 256051
|
|
|
|
| |
llvm-svn: 256034
|
|
|
|
| |
llvm-svn: 256033
|
|
|
|
|
|
|
| |
tracking bug:
https://llvm.org/bugs/show_bug.cgi?id=25872
llvm-svn: 256006
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
--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
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
llvm-svn: 255718
|
|
|
|
| |
llvm-svn: 255705
|
|
|
|
|
|
| |
categories
llvm-svn: 255687
|
|
|
|
|
|
|
| |
This allows more specialized formatters to still reuse the results
summarization display from the base class.
llvm-svn: 255676
|
|
|
|
|
|
|
|
|
|
|
|
| |
Both of these markers are used in the test suit for annotating when a
test needs multi threaded support. Previously they had slightly
different meening but they converged to the point where they are used
interchangably. This CL removes the ENABLE_STD_THREADS one to simplify
the test suite and avoid some confusion.
Differential revision: http://reviews.llvm.org/D15498
llvm-svn: 255641
|
|
|
|
|
|
|
|
|
|
| |
Reviewers: zturner
Subscribers: lldb-commits
Differential Revision: http://reviews.llvm.org/D15511
llvm-svn: 255584
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is the listener's spawned connection, not the listener itself.
(i.e. this is the test runner's receiving side of test event sockets).
A standard socket.error will just issue an INFO statement and continue.
Something other than a socket.error will get an ERROR: printed (and
also continue).
Hopefully this gets us more info and also handles the completely
to-be-expected scenario that the test inferior might go down at
any point.
llvm-svn: 255581
|
|
|
|
| |
llvm-svn: 255568
|
|
|
|
|
|
|
|
| |
This is leading to some kind of subtle issue related to local
functions and closures, so let's just go back to the old way for
now.
llvm-svn: 255567
|
|
|
|
|
|
| |
This reverts commit 30ed0826a1bb800454088ea1ae16c113a69b92b1.
llvm-svn: 255557
|
|
|
|
|
|
| |
This test is erroring out on a sequence call to a function.
llvm-svn: 255549
|
|
|
|
|
|
| |
Differential revision: http://reviews.llvm.org/D15061
llvm-svn: 255547
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|