summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test
Commit message (Collapse)AuthorAgeFilesLines
* Skipped IncompleteModulesTestCase on OS XTodd Fiala2016-01-231-2/+1
| | | | | | | | | | | | This is hitting an assert in clang when evaluating the module load. I am seeing it locally on Xcode 7.3 public Beta 1 and on the llvm.org Green Dragon buildbot supposedly running Xcode 7.0. Tracked by: https://llvm.org/bugs/show_bug.cgi?id=26267 llvm-svn: 258602
* fixed TestConsecutiveBreakpoints test on OS XTodd Fiala2016-01-233-6/+6
| | | | | | Also renamed directory and class name to fix typos. llvm-svn: 258601
* Fix missing function argument passthrough.Zachary Turner2016-01-231-1/+1
| | | | llvm-svn: 258592
* Decode files with UTF-8 in lldbutil.line_number.Zachary Turner2016-01-221-1/+2
| | | | | | | | Since Unicode support is different in Py2 and Py3, Py3 was throwing exceptions about being unable to decode the file with the default encoding. llvm-svn: 258588
* Un xfail TestSettings.test_run_args_and_env_vars_with_dwarfZachary Turner2016-01-221-1/+0
| | | | llvm-svn: 258587
* More fixes related to counting threads on Windows.Zachary Turner2016-01-223-86/+41
| | | | | | | | | | | | | | | The Windows 10 loader spawns threads at startup, so tests which count threads or assume that a given user thread will be at a specific index are incorrect in this case. The fix here is to use the standard mechanisms for getting the stopped thread (which is all we are really interested in anyway) and correlating them with the breakpoints that were set, and doing checks against those things. This fixes about 6 tests on Windows 10. llvm-svn: 258586
* XFail a test from TestConditionalBreak.py on Windows.Adrian McCarthy2016-01-221-2/+3
| | | | | | Filed a bug to investigate later: llvm.org/pr26265 llvm-svn: 258578
* XFail TestNamespaceLookup tests on Windows.Adrian McCarthy2016-01-221-1/+5
| | | | | | There's already a pr: https://llvm.org/bugs/show_bug.cgi?id=25819 llvm-svn: 258577
* fixed test suite crash when --platform-name doesn't start with 'remote-'Todd Fiala2016-01-221-9/+7
| | | | | | | | | | Also removes Darwin test case files from the expectedTimeout hard-coded file list. See: http://reviews.llvm.org/D16423 llvm-svn: 258542
* Revert "Enable test log collection from remote debug servers"Pavel Labath2016-01-221-18/+6
| | | | | | | | Unfortunately, this turns out not to be working on the lldb-server tests, as there the server is started in a different way. Since this was a bit of a hack to start with, I am removing it until I can solve the problem more holistically. llvm-svn: 258501
* Fix TestImport.py to work with Python 3.5.Adrian McCarthy2016-01-211-2/+4
| | | | | | Differential Revision: http://reviews.llvm.org/D16431 llvm-svn: 258448
* NFC. Corrects name of test class and a comment.Adrian McCarthy2016-01-211-2/+2
| | | | llvm-svn: 258433
* Remove assumptions that thread 0 is always the main thread.Zachary Turner2016-01-2118-147/+72
| | | | | | | | | | | | | | | | | Starting with Windows 10, the Windows loader is itself multi-threaded, meaning that the loader spins up a few threads to do process initialization before it executes main. Windows delivers these notifications asynchronously and they can come out of order, so we can't be sure that the first thread we get a notification about is actually the zero'th thread. This patch fixes this by requesting the thread stopped at the breakpoint that was specified, rather than getting thread 0 and verifying that it is stopped at a breakpoint. Differential Revision: http://reviews.llvm.org/D16247 llvm-svn: 258432
* Enable test log collection from remote debug serversPavel Labath2016-01-211-6/+18
| | | | | | | | | | | | | | | | | Summary: We already have the ability to collect the server logs when doing local debugging. This enables the collection of remote logs as well. This relies on specifying a relative path "server.log" for LLDB_DEBUGSERVER_LOG_FILE when starting remote platform. Since we always set the platform working directory to a fresh folder to avoid conflicts, the actual file path will always be different and we can pick the logs up from there. Reviewers: tfiala Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D16322 llvm-svn: 258414
* Mark arm/aarch64 specific xfails with expectedFailureLinux decoratorOmair Javaid2016-01-204-5/+8
| | | | | | | | | | | | | This patch marks some known failures and puts on expectedFailureLinux decorator to have testsuite xfail them. Affected tests are: test/functionalities/watchpoint/step_over_watchpoint.py test/functionalities/watchpoint/watchpoint_set_command/TestWatchLocationWithWatchSet.py test/tools/lldb-server/TestGdbRemoteSingleStep.py test/tools/lldb-server/TestGdbRemote_vCont.py llvm-svn: 258315
* Enable TestInlineStepping on linux i386Pavel Labath2016-01-201-2/+0
| | | | | | Test has been passing at least the last 200 buildbot runs. llvm-svn: 258305
* Enable TestConcurrentEvents on i386 linuxPavel Labath2016-01-201-1/+0
| | | | | | The test has been passing reliably the last 100 runs of the build bot. llvm-svn: 258304
* Fix for Bug 25338Ravitheja Addepally2016-01-193-11/+4
| | | | | | | | | | | | | | | | Summary: The issue arises because LLDB is not able to read the vdso library correctly. The fix adds memory allocation callbacks to allocate sufficient memory in case the requested offsets don't fit in the memory buffer allocated for the ELF. Reviewers: lldb-commits, clayborg, deepak2427, ovyalov, labath, tberghammer Differential Revision: http://reviews.llvm.org/D16107 llvm-svn: 258122
* Remove last XTIMEOUTs from android testsPavel Labath2016-01-192-6/+4
| | | | | | | | TestHelloWorld seems to be passing now as far as I can tell. TestExitDuringStep is still hanging. I have marked the relevant tests as flaky, which should handle the timeouts now as well. I'll be monitoring the buildbots for fallout. llvm-svn: 258114
* Remove skipIfLinuxClang decoratorPavel Labath2016-01-181-18/+0
| | | | | | it isn't used in the code anymore, and we're trying to cut down on the decorators. llvm-svn: 258049
* Guard against application of an XFAIL decorator on a classPavel Labath2016-01-181-0/+2
| | | | | | | | This does not work and causes the class to be silently skipped, which is a bad idea. This makes sure it cannot happen accidentaly. I've played with the idea of actually making the decorator work at class level, but it proved too magic to do at this moment. llvm-svn: 258048
* On non-Windows platforms, asm int 3 generates an eStopReasonSignal.Zachary Turner2016-01-151-1/+2
| | | | llvm-svn: 257959
* Fix TestDebugBreak.py.Zachary Turner2016-01-151-2/+3
| | | | | | | We can't assume that the main thread of an inferior has index 0, even in a single-threaded app. llvm-svn: 257946
* Small fixes to ensure TestLogging.py tests work with Python 3.5 as well as 2.7.Adrian McCarthy2016-01-151-3/+3
| | | | llvm-svn: 257931
* Fix decoration of TestConcurrentEventsPavel Labath2016-01-151-1/+35
| | | | | | | | | | TestConcurrentEvents was marked with a XFAIL decorator at class level, which actually does not work, and causes the class to be silently skipped everywhere. It seems that making it work at class level is quite a difficult task, so I will just move it to the individual test methods. I will follow this up with a commit which makes the decorator blow up in case someone tries to apply it to a class in the future. llvm-svn: 257901
* Fix detection of teardown hooks that are already bound.Adrian McCarthy2016-01-141-1/+1
| | | | llvm-svn: 257829
* Resubmit the fixes for TestProcessLaunch.py.Zachary Turner2016-01-142-21/+26
| | | | | | | I was calling the base class tearDown() function the wrong way which for some reason is ok on Python 3 but not on Python 2. llvm-svn: 257788
* Update some XFAILs after the 3.8->3.9 version changeTamas Berghammer2016-01-142-2/+2
| | | | llvm-svn: 257761
* XFAIL TestCommandScriptImmediateOutput on LinuxTamas Berghammer2016-01-141-0/+1
| | | | llvm-svn: 257755
* Revert changes to TestProcessLaunch.py as they are breaking a build.Zachary Turner2016-01-132-32/+20
| | | | llvm-svn: 257690
* Fix TestProcessLaunch for Python 3.Zachary Turner2016-01-132-20/+32
| | | | | | | | | | | | | | | | | | There were a number of problems preventing this from working: 1. The SWIG typemaps for converting Python lists to and from C++ arrays were not updated for Python 3. So they were doing things like PyString_Check instead of using the PythonString from PythonDataObjects. 2. ProcessLauncherWindows was ignoring the environment completely. So any test that involved launching an inferior with any kind of environment variable would have failed. 3. The test itself was using process.GetSTDOUT(), which isn't implemented on Windows. So this was changed to save the value of the environment variable in a local variable and have the debugger look at the value of the variable. llvm-svn: 257669
* Mark these tests on FreeBSD and Linux as non-flakey. We don't know that they areEnrico Granata2016-01-131-2/+0
| | | | llvm-svn: 257656
* Fix an issue where scripted commands would not actually print any of their ↵Enrico Granata2016-01-132-0/+45
| | | | | | | | output if an immediate output file was set in the result object via a Python file object Fixes rdar://24130303 llvm-svn: 257644
* [LLDB][MIPS] Fix TestDisassembleRawData.pySagar Thakur2016-01-131-7/+17
| | | | | | | | | | | Patch by Nitesh Jain. Summary: This patch adds check for the correctness of disassembling instruction for MIPS target. Reviewers: emaste, clayborg, ovyalov Subscribers: lldb-commits, mohit.bhakkad, sagar, bhushan, jaydeep Differential: http://reviews.llvm.org/D15915 llvm-svn: 257587
* [TestThreadJump] Adjust match sub-string after recent change.Siva Chandra2016-01-121-2/+1
| | | | | | | | | | Reviewers: zturner Subscribers: zturner, lldb-commits Differential Revision: http://reviews.llvm.org/D16125 llvm-svn: 257531
* 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
OpenPOWER on IntegriCloud