summaryrefslogtreecommitdiffstats
path: root/lldb/test
Commit message (Collapse)AuthorAgeFilesLines
...
* Check if "golden_output.txt" exists before trying to delete it rather than ↵Jim Ingham2014-03-191-5/+7
| | | | | | just raising an uncaught error. llvm-svn: 204258
* Put a workaround for flaky unwinder behavior on Darwin ↵Jim Ingham2014-03-191-4/+10
| | | | | | (<rdar://problem/16363195>). llvm-svn: 204254
* Add a test to check the C's constructor's name is C::C, which will fail ↵Jim Ingham2014-03-192-4/+71
| | | | | | | | | everywhere now, so mark as expected fail. And find another way to check that we hit our constructor breakpoint, so we don't need to expected fail the Disassembly tests. llvm-svn: 204209
* Don't use the Disassembly test to report the fact that we don't decorate upJim Ingham2014-03-191-4/+7
| | | | | | | constructors with their class name, that seems inessential. We can make another test specifically for this if we want to. llvm-svn: 204208
* Work around clang's ignoring __attribute ( align(16) ) in this test case.Jim Ingham2014-03-191-1/+6
| | | | llvm-svn: 204207
* Expected failure printing std::string::c_str() due to flubbing the typedef ↵Jim Ingham2014-03-191-6/+4
| | | | | | lookup. llvm-svn: 204206
* Inform users when *not* running dosep.ty multithreaded.Steve Pucci2014-03-161-1/+5
| | | | | | | | | The gain with multithreading is large, but turning it on requires an environment variable and so is hard for users to discover. This gives users a way to discover the feature by printing out a message when the environment variable is not set. llvm-svn: 204018
* Test cases for stepping out past frames with no debug info if that is turned on.Jim Ingham2014-03-154-0/+196
| | | | llvm-svn: 203993
* Refactor the Queues test case a little based on feedback from Jim.Jason Molenda2014-03-131-59/+135
| | | | | | Add queues tests for when libBacktraceRecording is absent. llvm-svn: 203864
* Also check if the queues are serial or concurrent.Jason Molenda2014-03-131-1/+7
| | | | llvm-svn: 203755
* Add a quick test case for some of the queues debugging support.Jason Molenda2014-03-133-0/+253
| | | | | | | It should only run on Darwin systems, and only when a couple of libraries are available. llvm-svn: 203754
* This commit reworks how the thread plan's ShouldStopHere mechanism works, so ↵Jim Ingham2014-03-131-0/+3
| | | | | | | | | | | | | | | that it is useful not only for customizing "step-in" behavior (e.g. step-in doesn't step into code with no debug info), but also the behavior of step-in/step-out and step-over when they step out of the frame they started in. I also added as a proof of concept of this reworking a mode for stepping where stepping out of a frame into a frame with no debug information will continue stepping out till it arrives at a frame that does have debug information. This is useful when you are debugging callback based code where the callbacks are separated from the code that initiated them by some library glue you don't care about, among other things. llvm-svn: 203747
* Need to use rm -rf on dSYM bundle directories.Jason Molenda2014-03-081-2/+3
| | | | llvm-svn: 203332
* Use predefined $(RM) in clean rule, and -r only for (expected) directoriesEd Maste2014-03-071-3/+4
| | | | llvm-svn: 203271
* Fix malloc thread step-out test on FreeBSDEd Maste2014-03-071-1/+9
| | | | | | | | | | | | | | | | After hitting the malloc() breakpoint on FreeBSD our top frame is actually an inlined function malloc_init. * frame #0: 0x0000000800dcba19 libc.so.7`malloc [inlined] malloc_init at malloc.c:5397 frame #1: 0x0000000800dcba19 libc.so.7`malloc(size=1024) + 9 at malloc.c:5949 frame #2: 0x00000000004006e5 test_step_out_of_malloc_into_function_b_with_dwarf`b(val=1) + 37 at main2.cpp:29 Add a heuristic to keep stepping out until we come to a non-malloc caller, before checking if it is our desired caller from the test code. llvm.org/pr17944 llvm-svn: 203268
* Fix test 'make clean' target for empty $(DSYM) on FreeBSDEd Maste2014-03-072-5/+7
| | | | | | | | | | | | | | | A freebsd issue with rm prevents '[g]make clean' from working if $(DSYM) is empty (fts_open(3) fails if passed an empty argument). To work around this, simplify the clean target by using three separate rm invocations: one for the common files, one for the case of non-empty $(DYLIB_NAME), and one for non-empty $(DSYM). Issue diagnosed (and reported to FreeBSD) by John Wolfe. llvm.org/pr17933 llvm-svn: 203253
* Add decorator for recent FreeBSD failureEd Maste2014-03-071-0/+1
| | | | | | llvm.org/pr19075 llvm-svn: 203245
* This commit provides support for running the dosep.ty test driver with ↵Steve Pucci2014-03-073-22/+78
| | | | | | | | | | | | | | multiple threads. It speeds up running the full test suite on my HP z620 Ubuntu machine with 32 hyperthreaded CPUs from 11 minutes to about 1m13s (about 9x). The default behavior is to run single-threaded as before. If the environment variable LLDB_TEST_THREADS is set, a Python work queue is set up with that many worker threads. To avoid collisions within a test directory where multiple tests make use of the same prebuilt executable, the unit of work for the worker threads is a single directory (that is, all tests within a directory are processed in the normal serial way by a single thread). tfiala & I have run this way a number of times; the only issue I found was that the TestProcessAttach.py test failed once, when attempting to attach to the process "a.out" by name. I assume this is because some other thread was running an executable of that name at the same time, and we were attempting to attach to the wrong one, so I changed that test to use a different executable name (that change is also included in this commit). llvm-svn: 203180
* Modified some test annotations so that tests on Linux that should be skipped ↵Todd Fiala2014-03-043-4/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | don't show up as XFAIL. The following two tests showed up as XFAIL even though they should always be skipped on Linux, due to the @unittest2.expectedFailure annotation appearing above the @dsym_test annotation: TestObjCNewSyntax.ObjCNewSyntaxTestCase.test_expr_with_dsym TestBlocks.BlocksTestCase.test_expr_with_dsym. For those two, I simply moved the @dsym_test annotation to the top so that it would be marked for skip ahead of being marked for XFAIL. TestObjCNewSyntax.ObjCNewSyntaxTestCase.test_expr_with_dwarf I marked as @skipIfLinux since my understanding is that isn't a valid test to run on Linux. So rather than categorize as a fail (i.e. something wrong to be fixed), just skip it. (My recent changes to Linux tests have been following that model: if it could never work, skip; if it's broken, mark XFAIL so we can easily track, fix, notice the fix and adjust accordingly). TestDeadStrip.DeadStripTestCase.test_with_dwarf I had previously marked as XFAIL but this would never work on Linux with the current linker AFAICT. Marked it as skip. llvm-svn: 202788
* Update test class name and comment to match testEd Maste2014-03-031-2/+2
| | | | llvm-svn: 202718
* Converted TestDeadStrip.py to be expected failure on Linux.Todd Fiala2014-02-281-1/+1
| | | | llvm-svn: 202522
* Adjust TestExprDoesntBlock.py to be expected failure on Linux.Todd Fiala2014-02-281-1/+1
| | | | | | | | I suspect I may have misrun the test previously for check-in r202456 re: pr15258. This test fails consistently on my end. I changed the test to expected failure on Linux. llvm-svn: 202517
* Enabled TestSetWatchlocation.py on Linux.Todd Fiala2014-02-281-1/+0
| | | | | | | This worked 25 out of 25 times for me on Ubuntu 12.04 LTS x86_64 built with gcc 4.8.2 and the July 2013 libedit. llvm-svn: 202516
* Converted TestRegisterVariables to run on Linux and skip with clang.Todd Fiala2014-02-281-1/+1
| | | | | | | | TestRegisterVariables.test_with_dwarf_and_run_command was being skipped on Linux due to issues with clang. I converted it to a @expectedFailureClang and no longer skip on Linux. llvm-svn: 202515
* Converted TestConstVariables expected failure to @expectedFailureClang.Todd Fiala2014-02-281-2/+1
| | | | | | | | | TestConstVariables.py was disabled on Linux and marked as unconditional expected failure. This change removes the Linux disable and makes the expected failure conditional on using clang. The test runs fine on gcc-built lldb. llvm-svn: 202514
* Restore signal delivery to the inferior on FreeBSDEd Maste2014-02-281-1/+0
| | | | | | | This was broken in the threaded inferior implementation for FreeBSD (r196787) and caused FreeBSD to resume always with no signal. llvm-svn: 202513
* Enable TestExitDuringBreak.test_with_dwarf on Linux.Todd Fiala2014-02-281-1/+0
| | | | | | | | | | This test passed 50 out of 50 times for me on Unbuntu 12.04 LTS x86_64 with lldb built using gcc 4.8.2 and July 2013 libedit. This is related to: http://llvm.org/bugs/show_bug.cgi?id=16170 llvm-svn: 202512
* Adjust TestConcurrentEvents.py test running for Linux.Todd Fiala2014-02-281-21/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Related to this bug: http://llvm.org/bugs/show_bug.cgi?id=16714 On TOT lldb svn r202507, I found several of the tests disabled within TestConcurrentEvents.py to run fine, and several of them to fail 100% of the time on my system (25 out of 25 times). This changes the following tests for Linux: Enables (these all work consistently): * test_many_watchpoints_dwarf * test_signal_watch_break_dwarf (line 250) * test_signal_watch_break_dwarf (line 260 - same named test?) * test_crash_with_watchpoint_dwarf * test_crash_with_watchpoint_breakpoint_signal_dwarf * test_delayed_crash_with_breakpoint_watchpoint_dwarf Marks as expected failure (these all fail consistently): * test_many_watchpoints_dwarf * test_watch_break_dwarf * test_delay_watch_break_dwarf * test_watch_break_dwarf_delay * test_signal_watch_dwarf * test_delay_signal_watch_dwarf * test_signal_delay_watch_dwarf * test_two_breakpoints_one_watchpoint_dwarf * test_breakpoints_delayed_breakpoint_one_watchpoint_dwarf * test_two_watchpoint_threads_dwarf * test_watchpoint_with_delay_watchpoint_threads_dwarf * test_two_watchpoints_one_breakpoint_dwarf * test_two_watchpoints_one_delay_breakpoint_dwarf * test_watchpoint_delay_watchpoint_one_breakpoint_dwarf * test_two_watchpoints_one_signal_dwarf * test_signal_watch_break_dwarf llvm-svn: 202511
* Enabled TestBreakAfterJoin.py on Linux.Todd Fiala2014-02-281-1/+0
| | | | | | | | | | This is related to: http://llvm.org/bugs/show_bug.cgi?id=16170 This test ran successfully 40 out of 40 times on Ubuntu 12.04 LTS x86_64. llvm-svn: 202508
* Change TestStopHookMechanism to @expectedFailureLinux.Todd Fiala2014-02-281-1/+1
| | | | | | | | | Similar to my previous check-in related to: http://llvm.org/bugs/show_bug.cgi?id=15037 10 out of 10 runs of this failed. Mark it XFAIL. llvm-svn: 202507
* Marked linux TestStopHookMultipleThreads as expected failure.Todd Fiala2014-02-281-1/+1
| | | | | | | | | | Related to this bug: http://llvm.org/bugs/show_bug.cgi?id=15037 Previously this was marked as skipped. I tried running it 10 times in a row and it failed every time. Switched it to XFAIL. llvm-svn: 202506
* Re-enable TestExprDoesntBlock.py on Linux.Todd Fiala2014-02-281-1/+1
| | | | | | | | | | This is related to: http://llvm.org/bugs/show_bug.cgi?id=15258 I ran this test 10 times successfully against Ubuntu 12.04 LTS x86_64 with lldb built with gcc 4.8.2 and July 2013 libedit. llvm-svn: 202456
* Enable TestCallThatRestarts test on Linux.Todd Fiala2014-02-281-1/+0
| | | | | | | | | | This is related to: http://llvm.org/bugs/show_bug.cgi?id=15278 I ran this 20 times in a row without failure at svn r202440 on Ubuntu 12.04 LTS x86_64 using July 2013 libedit and gcc 4.8.2. llvm-svn: 202448
* Re-enable TestMultithreaded.py test on Linux.Todd Fiala2014-02-281-1/+0
| | | | | | | | I could not get http://llvm.org/bugs/show_bug.cgi?id=16016) to fail on my end running 10 times in a row. Re-enabling the test. llvm-svn: 202446
* Make TestStdCXXDisassembly.StdCXXDisassembleTestCase work with libc++Enrico Granata2014-02-251-4/+5
| | | | | | <rdar://problem/16115219> llvm-svn: 202180
* Remove TestConnectRemote decorator for FreeBSDEd Maste2014-02-241-1/+0
| | | | | | | | Failure is not reproducible on ToT LLDB locally or on the buildbot. llvm.org/pr18313 llvm-svn: 202043
* Stop skipping test on FreeBSD that no longer failsEd Maste2014-02-221-1/+0
| | | | | | llvm.org/pr17232 llvm-svn: 201928
* On FreeBSD "x86_64" is spelled "amd64"Ed Maste2014-02-201-1/+4
| | | | llvm-svn: 201802
* Treat 'amd64' as 'x86_64' as done for other testsEd Maste2014-02-191-2/+3
| | | | | | | | And add a decorator for llvm.org/pr18200 Patch by John Wolfe. llvm-svn: 201708
* FreeBSD hardware watchpoint implementationEd Maste2014-02-1914-37/+0
| | | | | | | | | | | | | | | Implement x86_64 debug register read/write in support of hardware watchpoints. Hoist LinuxThread::TraceNotify code back into POSIXThread::TraceNotify() Patch by John Wolfe. We still need to rework this later to avoid the #ifdef FreeBSD. llvm-reviews.chandlerc.com/D2572 llvm.org/pr16706 llvm-svn: 201706
* Update decorator for test that still fails with FreeBSD Watchpoint supportEd Maste2014-02-191-1/+1
| | | | | | llvm.org/pr18832 llvm-svn: 201705
* <rdar://problem/15960553>Enrico Granata2014-02-183-0/+85
| | | | | | Fix a bug where calling SBFrame::FindValue() would cause a copy of all variables in the block to be inserted in the frame's variable list, regardless of whether those same variables were there or not - which means one could end up with a frame with lots of duplicate copies of the same variables llvm-svn: 201614
* Eliminate kernel warning when running tests on FreeBSDEd Maste2014-02-181-10/+4
| | | | | | | | | | | | | | | pexpect had a hack to work around some old buggy platforms, and as a result of the hack running the tests on FreeBSD produced a stream of kernel warnings in the system log: Feb 5 17:19:11 feynman kernel: WARNING pid 11323 (python2.7): ioctl sign-extension ioctl ffffffff80087467 The hack has now been removed upstream, so remove it here too. llvm.org/pr18749 llvm-svn: 201603
* <rdar://problem/16006373>Enrico Granata2014-02-151-7/+7
| | | | | | | Revert the spirit of r199857 - a convincing case can be made that overriding a summary's format markers behind its back is not the right thing to do This commit reverts the behavior of the code to the previous model, and changes the test case to validate the opposite of what it was validating before llvm-svn: 201455
* Adjust logging test case after r201372Ed Maste2014-02-141-1/+0
| | | | | | | The final "HandleCommand, command succeeded" for "log disable lldb" doesn't make it to the log file before the command takes effect. llvm-svn: 201422
* Update decorators for tests that still fail with FreeBSD Watchpoint supportEd Maste2014-02-142-2/+2
| | | | | | | | llvm.org/pr18832 Reported by John Wolfe llvm-svn: 201418
* Re-enable TestAbbreviations.py on Linux after test fix.Todd Fiala2014-02-131-1/+0
| | | | | | See http://llvm.org/bugs/show_bug.cgi?id=18816. llvm-svn: 201357
* Fixed a test suite failure on Darwin due to logging issues.Greg Clayton2014-02-131-1/+1
| | | | llvm-svn: 201356
* Remove decorator for fixed testEd Maste2014-02-131-1/+0
| | | | | | llvm.org/pr18805 fixed by r201270 llvm-svn: 201284
* Fixed the TestLogging test.Greg Clayton2014-02-121-1/+8
| | | | llvm-svn: 201273
OpenPOWER on IntegriCloud