summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test
Commit message (Collapse)AuthorAgeFilesLines
* Fix TestThreadJump on Windows.Zachary Turner2016-01-121-2/+1
| | | | | | | | The system can create threads for a system threadpool, so there is no guarantee that the thread that is stopped is thread 1. So use a more robust check. llvm-svn: 257513
* Fix for TestNoreturnUnwind.py on i386Ravitheja Addepally2016-01-121-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Summary: The testcase TestNoreturnUnwind.py was failing because the unwind from the vdso library was not successful for clang compiler while it was passing for gcc. It was passing for gcc since the unwind plan used was the assembly plan and the ebp register was set by the main function in case of gcc and was not used by the functions in the call flow to the vdso, whereas clang did not emit assembly prologue for main and so the assembly unwind was failing. Normally in case of failure of assembly unwind, lldb switches to EH CFI frame based unwinding, but this was not happening for the first frame. This patch tries to fix this behaviour by falling to EH CFI frame based unwinding in case of assembly unwind failure even for the first frame. The test is still marked as XFAIL since it relys on the fix of another bug. Reviewers: lldb-commits, jingham, zturner, tberghammer, jasonmolenda Subscribers: jasonmolenda Differential Revision: http://reviews.llvm.org/D15046 llvm-svn: 257465
* Xfail some Arm-Linux specific failuresOmair Javaid2016-01-114-3/+10
| | | | | | | | | | Updated expectedFailureLinux decorator to reflect architecture Marked some triaged failures as xfails on arm with updated expectedFailureLinux decorator Differential revision: http://reviews.llvm.org/D15893 llvm-svn: 257405
* Don't run dwo tests for windows targets.Zachary Turner2016-01-111-1/+2
| | | | | | | | | | -gsplit-dwarf is not implemented by clang on Windows. As such, all the dwo tests are having the -gsplit-dwarf command line option completely ignored, and the result is you get regular dwarf debug information, and it's just running the exact same tests twice, doubling the length of the test suite for no good reason. llvm-svn: 257363
* Replace accidental DOS (and mixed) line endings in a few text filesDimitry Andric2016-01-111-31/+31
| | | | | | | | | | | | | | Summary: Similar to rL256704 and rL256707, fix a few text files which were accidentally checked in with DOS line endings, or mixed line endings. Reviewers: jingham, emaste Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D16027 llvm-svn: 257361
* Fix TestMiniDump.py for Python 2/3 (and for a change to debug info)Adrian McCarthy2016-01-111-3/+3
| | | | | | Differential Revision: http://reviews.llvm.org/D16017 llvm-svn: 257342
* Mark TestChangeValueAPI as flaky on linux (pr25652)Pavel Labath2016-01-111-0/+1
| | | | llvm-svn: 257329
* Skip TestEvents on linux completelyPavel Labath2016-01-111-1/+1
| | | | | | | The test hangs/crashes/fails because it does not use the listener API in a way that LLDB expects. I don't really know if this is the fault of LLDB of the test... llvm-svn: 257323
* Remove CRLF line endings from test_common.hPavel Labath2016-01-111-44/+44
| | | | llvm-svn: 257321
* Centralize the handling of attach permissions on linux in testsPavel Labath2016-01-1110-134/+42
| | | | | | | | | | | | | | | Summary: On linux we need the process to give us special permissions before we can attach to it. Previously, the code for this was copied into every file that needed it. This moves the code to a central place to reduce code duplication. Reviewers: clayborg Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D15992 llvm-svn: 257319
* Writing a test case for r257234 I found another place that wasJim Ingham2016-01-093-0/+70
| | | | | | | assuming a ValueObject always has a process. So this is that fix and the test case. llvm-svn: 257242
* Fiddling with Pavel's fix for getting the breakpoint right when there's ↵Jim Ingham2016-01-091-2/+1
| | | | | | | | | | | debug info for sleep. I prefer to use "-p" over using line_number and then setting by line because it's makes it possible to see what the breakpoint is at the site where you make the breakpoint. So I switched it back to -p but specified the source file as well, which is an "all within lldb" way of doing what Pavel's fix did. llvm-svn: 257235
* Fix TestDebugBreak.py failure with gcc, for loop declarations are not ↵Ying Chen2016-01-081-2/+2
| | | | | | | | | allowed by default with gcc - fix buildbot breakage after r257186 - move declaration outside of for loop llvm-svn: 257228
* Remove XFAIL from a few tests that have been fixed on Windows.Zachary Turner2016-01-083-3/+0
| | | | llvm-svn: 257219
* XFAIL 2 more tests based on SWIG version.Zachary Turner2016-01-082-0/+4
| | | | | | | There's a bug in versions of SWIG prior to 3.0.8 that prevent these tests from succeeding with Python 3.x llvm-svn: 257208
* Remove XFAIL from TestThreadStates on Windows.Zachary Turner2016-01-081-1/+0
| | | | llvm-svn: 257207
* Treat an embedded int3/__debugbreak() as a breakpoint on Windows, includes a ↵Adrian McCarthy2016-01-083-0/+85
| | | | | | cross-platform test. llvm-svn: 257186
* Fix TestBatchMode for gccPavel Labath2016-01-081-1/+2
| | | | | | | gcc by default does not accept for loop declarations in C files (one must choose C99 mode first, which we don't). Place the declaration outside the loop, to make this code more conformant. llvm-svn: 257166
* Another fix for TestBatchMode on linuxPavel Labath2016-01-081-0/+17
| | | | | | | On locked down systems (such as our buildbot) one needs to do a special dance to allow attaching to processes. This commit adds this code to the TestBatchMode inferior. llvm-svn: 257165
* Fix TestBatchMode on linuxPavel Labath2016-01-081-1/+2
| | | | | | | | | | New test introduced in r257120 was failing on linux. The reason for that the regex for setting the breakpoint was being applied to the "default file", which in this case was the asm file containing the definition of the sleep() syscall (because after attach, we are stopped in the sleep function). I have changed this use the more customary way of setting the breakpoint and specifying the source file name explicitly. llvm-svn: 257160
* Fix a glitch in the Driver's batch mode when used with "attach". Jim Ingham2016-01-082-14/+116
| | | | | | | | | | | | | | Batch mode is supposed to stop execution and return control to the user when an exceptional stop occurs (crash, signal or instrumentation). But attach always stops with a SIGSTOP on OSX (maybe on Linux too?) which would short circuit the rest of the commands given. This change allows a command result object to indicate that it expected to leave the process stopped with an exceptional stop reason, and it is okay for batch mode to keep going. <rdar://problem/22243143> llvm-svn: 257120
* XFAIL TestMultithreaded on linuxPavel Labath2016-01-071-1/+1
| | | | | | Test sometimes fails even during the reruns, upgrading to xflaky to xfail. llvm-svn: 257068
* Remove some Windows->Android XTIMEOUTsPavel Labath2016-01-071-5/+0
| | | | llvm-svn: 257052
* XFAIL TestEvents.test_add_listener_to_broadcasterPavel Labath2016-01-071-1/+1
| | | | | | Upgrade flaky to xfail, as the test sometimes fails even during the rerun. llvm-svn: 257050
* fixup lldbinline-style tests to clean up Makefiles and *.d filesTodd Fiala2016-01-061-4/+4
| | | | | | | | | The lldbinline inline-test mechanism will create a Makefile if one does not exist in the test directory. This Makefile and its *.d files were not getting cleaned up after a test run, leaving trash in the source tree. llvm-svn: 256961
* Remove XTIMEOUT from TestMultithreaded on linuxPavel Labath2016-01-062-5/+2
| | | | | | instead, mark the test as expected flaky, which will trigger a rerun in case the test hangs. llvm-svn: 256935
* Fix a bug in lldbutil.expect_state_changesPavel Labath2016-01-061-10/+18
| | | | | | | | The logic for skipping over the stop-and-restart events was incorrect as it was also skipping the expectations. Implement it properly. No test is affected by this as they were not encountering these events, but I encountered this issue when trying to use this function in a new test. llvm-svn: 256928
* XFAIL TestMiSymbol on linuxPavel Labath2016-01-061-0/+1
| | | | | | new test introduced in r256863 fails on linux. llvm-svn: 256925
* Apply missed changes from svn r256863 "Add support for "source info" and use ↵Dawn Perchik2016-01-062-5/+5
| | | | | | | | | it to fix MI's -symbol-list-lines.". Patch is part of Differential Revision: http://reviews.llvm.org/D15593 Differential Revision: http://reviews.llvm.org/D15904 llvm-svn: 256877
* Add support for "source info" and use it to fix MI's -symbol-list-lines.Dawn Perchik2016-01-053-4/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* Fix a typo in lldbutil.pyPavel Labath2016-01-051-1/+1
| | | | llvm-svn: 256851
* Mark a test_lldbmi_gdb_set_target_async_on as flaky on linuxPavel Labath2016-01-051-0/+1
| | | | | | Test fails in about 1% of buildbot runs. Marking as flaky to avoid the noise. llvm-svn: 256835
* Remove XTIMEOUT from TestEvents on linuxPavel Labath2016-01-051-1/+0
| | | | | | | 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
* Remove old flaky test rerun logicPavel Labath2016-01-051-23/+3
| | | | | | | | | | | | | | 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
* Remove XTIMEOUT from TestRegisters on linuxPavel Labath2016-01-041-1/+0
| | | | | | | 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
* Remove XTIMEOUT from TestThreadStepOut on linuxPavel Labath2016-01-041-1/+0
| | | | | | The whole test is skipped already, so it's not running anyway. llvm-svn: 256752
* Remove XTIMEOUT from TestHelloWorld on linuxPavel Labath2016-01-041-3/+0
| | | | | | | 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
* Remove XTIMEOUT from TestExitDuringStep on linuxPavel Labath2016-01-041-1/+0
| | | | | | | 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
* Remove XTIMEOUT from TestCreateAfterAttach on linuxPavel Labath2016-01-041-1/+0
| | | | | | | 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
* Remove TestConnectRemote from XTIMEOUTsPavel Labath2016-01-041-1/+0
| | | | | | The test in question was removed in r249613. llvm-svn: 256741
* Allow test decorators to use lists (and not_in(list)) for archesAdrian McCarthy2015-12-221-3/+8
| | | | | | Differential Revision: https://mail.google.com/mail/u/0/?zx=w4areffgjbgg#inbox/151cb6afe6169bb0 llvm-svn: 256283
* XFAIL TestCppNsImport on FreeBSDEd Maste2015-12-221-0/+1
| | | | | | | | | 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
* Add expectedFailureFreeBSD to an additional thread state test failing on FreeBSDEd Maste2015-12-221-0/+1
| | | | | | This new failure has been noted in the existing PR, llvm.org/pr15824 llvm-svn: 256268
* skip TestEvents.py on DarwinTodd Fiala2015-12-221-0/+1
| | | | | | | | | | | | 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
* test infra: fix lldbinline tests to work with rerunTodd Fiala2015-12-225-2/+42
| | | | | | | Fixes: https://llvm.org/bugs/show_bug.cgi?id=25922 llvm-svn: 256255
* Improve error handling for `frame select` command when there are too many ↵Adrian McCarthy2015-12-221-0/+1
| | | | | | | | | | 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
* Add expectedFailureFreeBSD to tests failing in the same way as on LinuxEd Maste2015-12-221-0/+3
| | | | | | llvm.org/pr25819 llvm-svn: 256250
* [TestCPPAuto] On linux, we need -fno-limit-debug-info.Siva Chandra2015-12-193-1/+6
| | | | | | | | | | | | 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
* Add support for seeing through clang::AutoType in ClangASTContextEnrico Granata2015-12-183-0/+45
| | | | | | | | This allows LLDB to deal correctly with expression result variables declared via the C++11 'auto' keyword rdar://problem/23960490 llvm-svn: 256051
* Add a test case that validates that my change in r255603 does the right thingEnrico Granata2015-12-183-0/+85
| | | | llvm-svn: 256034
OpenPOWER on IntegriCloud