summaryrefslogtreecommitdiffstats
path: root/lldb/test/functionalities/thread
Commit message (Collapse)AuthorAgeFilesLines
...
* XFAILing a single test in TestConcurrentEventsPavel Labath2015-04-221-0/+1
| | | | | | | apparently, TestConcurrentEvents is still not fixed. One test has failed on Linux i386 build. Will disable the failing test on i386 for now, and see how it goes.. llvm-svn: 235504
* Enable TestConcurrentEvents on LinuxPavel Labath2015-04-221-16/+0
| | | | | | | After the latest changes in NativeProcessLinux, these tests should be stable now. Please revert (and let me know) if any issue crops up. llvm-svn: 235502
* NativeProcessLinux: Merge operation and monitor threadsPavel Labath2015-04-201-1/+0
| | | | | | | | | | | | | | | | | Summary: This commit moves the functionality of the operation thread into the new monitor thread. This is required to avoid a kernel race between the two threads and I believe it actually makes the code cleaner. Test Plan: Ran the test suite a couple of times, no regressions. Reviewers: ovyalov, tberghammer, vharron Subscribers: tberghammer, lldb-commits Differential Revision: http://reviews.llvm.org/D9080 llvm-svn: 235304
* Replace sys.platform skips in tests with @skip decorators which check ↵Robert Flack2015-03-3011-20/+20
| | | | | | | | | | | | | | | | against remote platform. Adds @skipIfPlatform and @skipUnlessPlatform decorators which will skip if / unless the target platform is in the provided platform list. Test Plan: ninja check-lldb shows no regressions. When running cross platform, tests which cannot run on the target platform are skipped. Differential Revision: http://reviews.llvm.org/D8665 llvm-svn: 233547
* XFAIL tests that are known to fail occasionally on LinuxVince Harron2015-03-053-0/+3
| | | | | | | | Trying to get the build green so we can notice new failures easier. Differential Revision: http://reviews.llvm.org/D8039 llvm-svn: 231407
* Fixed pthread linking errors in test binariesVince Harron2015-02-284-0/+4
| | | | | | | | | | | Fixes these tests: TestBreakAfterJoin.py TestCreateDuringStep.py TestExitDuringBreak.py TestMultipleBreakpoints.py llvm-svn: 230828
* Remove use_pthread option from getBuildFlags in the test environmentTamas Berghammer2015-02-254-0/+4
| | | | | | | | | | | Removing the option to require the usage of pthread based on an argument of the getBuildFlags method in lldbtest.py because it can be specified by a variable in the makefile for the given test case. Using the variable in the makefile works in all supported platforms. Differential revision: http://reviews.llvm.org/D7861 llvm-svn: 230493
* Mark several tests as XFAIL with new expectedFailureLLGS decorator since ↵Chaoren Lin2015-02-036-1/+11
| | | | | | they are failing in Darwin for the same reason. llvm-svn: 227925
* Modify ThreadStateCoodrinator in order to resume threads if stop wasn't ↵Chaoren Lin2015-02-031-1/+1
| | | | | | requested. llvm-svn: 227924
* TestConcurrentEvents - delay threads not workingVince Harron2014-11-131-4/+4
| | | | | | | | | | | Part of TestConcurrentEvents starts threads that are supposed to be delayed by one second. Test was adding "delay" threads to the "actions" thread list instead of the "delay_actions" list, which caused them to be started without delay. llvm-svn: 221859
* Skip test that's hanging on FreeBSD until it can be investigatedEd Maste2014-10-291-0/+3
| | | | | | llvm.org/pr21411 llvm-svn: 220856
* Fix the TestCreateAfterAttach test for llgs-local on ptracer lock-down.Todd Fiala2014-10-271-0/+19
| | | | llvm-svn: 220661
* Get test executables compiling on Windows.Zachary Turner2014-08-134-7/+5
| | | | | | | | | | | | | | Many of the test executables use pthreads directly. This isn't portable on Windows, so this patch converts these test to use C++11 threads and mutexes. Since Windows' implementation of std::thread classes throw and catch from header files, this patch also disables exceptions when compiling with clang on Windows. Reviewed by: Todd Fiala, Ed Maste Differential Revision: http://reviews.llvm.org/D4816 llvm-svn: 215562
* We were turning off all these tests on OSX and FreeBSD because of a known ↵Jim Ingham2014-07-241-15/+28
| | | | | | | | (and fairly unimportant) bug. Keep a test for that bug, but let the useful parts of the test run anyway. llvm-svn: 213875
* Fix a few typos.Bruce Mitchener2014-06-271-1/+1
| | | | llvm-svn: 211851
* Do not rely on invalid pthread API use in thread testEd Maste2014-04-092-24/+22
| | | | | | | | | | Calling mutex_lock from one thread and then mutex_unlock from another is not permitted. Replace the awkward mutex usage with a mutex and condition variable. llvm.org/pr18061 llvm-svn: 205900
* Correct typo: waychpoint -> watchpointEd Maste2014-04-071-1/+1
| | | | llvm-svn: 205719
* Add failure decoratorsEd Maste2014-04-041-0/+2
| | | | | | | | | These tests started failing on FreeBSD after r205497 "Make the fail messages" llvm.org/pr19347 llvm-svn: 205652
* 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
* FreeBSD hardware watchpoint implementationEd Maste2014-02-191-18/+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
* Remove decorators for llvm.org/pr17920 fixed by r200646Ed Maste2014-02-112-8/+0
| | | | llvm-svn: 201167
* Update decorator for FreeBSD failure pr18066Ed Maste2014-02-111-1/+1
| | | | | | | | The test expects the inferior to have exited, but it is still stopped. llvm.org/pr18066 llvm-svn: 201166
* Remove failure decorators for FreeBSD bugEd Maste2014-02-021-5/+0
| | | | | | | | | | | | | The issue described in llvm.org/pr18065 is actually due to FreeBSD bug theads/186309 [1], which is now fixed in FreeBSD SVN r261354 [2] and will be merged to release branches shortly. Diagnosed and fixed by John Wolfe. [1] http://www.freebsd.org/cgi/query-pr.cgi?pr=186309 [2] http://svnweb.freebsd.org/base?view=revision&revision=261354 llvm-svn: 200648
* Add decorator for FreeBSD test failure pr18522Ed Maste2014-01-181-0/+1
| | | | llvm-svn: 199550
* Undo r199448, already implemented in r199426Ed Maste2014-01-171-1/+0
| | | | llvm-svn: 199449
* Link thread-specific breakpoint test against libpthreadEd Maste2014-01-171-0/+1
| | | | llvm-svn: 199448
* Fix bug in Linux remote dynamic loader setup and fix test.Todd Fiala2014-01-162-2/+4
| | | | | | | | | | | | | | | | | | | | | Part 1 changes PlatformLinux::CreateInstance to always create with is_host=false; that method is only used as the plug-in creator method associated with the remote-linux platform plugin, and should therefore always be remote. Part 1 patch by Steve Pucci. Part 2: fix a test break on linux. In test/functionalities/thread/thread_specific_break, when using gcc, either C99 mode would need to be enabled, or the code would need to change. I changed a couple loop variable definitions to conform to pre-C99 to simplify testing the fix. The second issue was the necessity to include -lpthread as a linker option in the Makefile. Any issues with that part are due to me (Todd Fiala). llvm-svn: 199426
* Fix a bug where if we stop but nobody says there was a reason for the stop, ↵Jim Ingham2014-01-153-0/+120
| | | | | | | | | | | | | we would return control to the user anyway. This was put in to handle monitors that would say there was no stop reason when you first attached to them. But it broke the case where you hit a thread specific breakpoint on many threads, but NOT the one specified in the breakpoint. I work around this by only doing the junky override when the StopID is 0 - i.e. on first attach. This commit also adds a test for thread specific breakpoints. llvm-svn: 199290
* Massive test suite cleanup to stop everyone from manually having to compute ↵Greg Clayton2013-12-1012-12/+12
| | | | | | | | | | "mydir" inside each test case. This has led to many test suite failures because of copy and paste where new test cases were based off of other test cases and the "mydir" variable wasn't updated. Now you can call your superclasses "compute_mydir()" function with "__file__" as the sole argument and the relative path will be computed for you. llvm-svn: 196985
* test: Update decorators for FreeBSD failures with threaded inferior supportEd Maste2013-12-096-10/+10
| | | | | | | llvm.org/pr18190 llvm.org/pr18191 llvm-svn: 196792
* Add decorator for FreeBSD watchpoint failureEd Maste2013-12-091-0/+1
| | | | | | llvm.org/pr16706 llvm-svn: 196781
* Added two new test case decorator functions: @skipIfRemote and ↵Greg Clayton2013-12-051-1/+21
| | | | | | | | | | @skipIfRemoteDueToDeadlock. @skipIfRemote is used to decorate test cases that don't make sense to run remotely. @skipIfRemoteDueToDeadlock indicates these tests need to be looked at and currently deadlock the running of the test suite when run on remote systems. These issues should be fixed soon. llvm-svn: 196543
* test: Decorators for pr17910Ed Maste2013-12-022-14/+14
| | | | | | | | | | | | A number of tests fail to build on FreeBSD because the test build script defaults to libstdc++ for clang. On FreeBSD the libstdc++ is rather old and libc++ should be used instead. (These tests previously had an @expectedFailureFreeBSD decorator for pr16696, the umbrella PR for the lack of threaded inferior support on FreeBSD. The work to add that support will be committed soon.) llvm-svn: 196101
* Add decorator for FreeBSD failing test due to pr18061Ed Maste2013-11-261-1/+1
| | | | | | | | | | The test code locks mutexes from one thread and unlocks them from a different one, which is not valid (it's either undefined behaviour or is required to return an error). See http://pubs.opengroup.org/onlinepubs/9699919799/functions/pthread_mutex_lock.html llvm-svn: 195707
* This only fails on Darwin ; thanks Jim for pointing that outEnrico Granata2013-11-011-2/+2
| | | | llvm-svn: 193843
* Thread::SetState() is not being called upon hitting the breakpointEnrico Granata2013-10-311-0/+2
| | | | | | | Given that, this test will never pass Marking as expected failure pending a fix llvm-svn: 193830
* Fix the thread jump test case for 32-bit inferiors. A jump was going back to ↵Matt Kopec2013-09-261-3/+4
| | | | | | a function call using a source line number. However, the parameters being passed to the function were setup before the instruction we jumped to. In other words, the source line was associated with assembly after the function parameters had been setup for the function to be called. llvm-svn: 191457
* Make threading tests not depend on the currently selected threadDaniel Malea2013-09-193-15/+32
| | | | | | | | | - tests are now anostic to the currently selected thread, as that is a frontend (i.e. driver) decision - this is in preparation to a fix to POSIXThread::BreakNotify that will be committed shortly Reviewed by: Matt Kopec llvm-svn: 191041
* test: Update FreeBSD failure decoratorsEd Maste2013-09-131-0/+1
| | | | | | | | | | | | | | | llvm.org/pr15261 missing size for static arrays llvm.org/pr15278 expressions generating signals llvm.org/pr15824 thread states aren't properly maintained llvm.org/pr16696 threaded inferior debugging not yet on FreeBSD llvm.org/pr17214 inline stepping fails on FreeBSD llvm.org/pr17225 Clang assertion failure llvm.org/pr17226 frame info lost after failed expression evaluation llvm.org/pr17228 test timeout The first three are existing Linux issues that also affect FreeBSD. llvm-svn: 190698
* Added a 'jump' command, similar to GDBs.Richard Mitton2013-09-124-0/+126
| | | | | | | | | This allows the PC to be directly changed to a different line. It's similar to the example python script in examples/python/jump.py, except implemented as a builtin. Also this version will track the current function correctly even if the target line resolves to multiple addresses. (e.g. debugging a templated function) llvm-svn: 190572
* Disabling tests affected by llvm.org/pr16170 on LinuxDaniel Malea2013-09-092-0/+2
| | | | | | - occasional lldb hangs are causing noisy buildbots and trouble in the (Debian/Ubuntu) package builder llvm-svn: 190355
* Re-enable check previously disabled due to llvm.org/pr16603Daniel Malea2013-08-071-4/+3
| | | | llvm-svn: 187890
* Centralizing Intel compiler detection logic in lldbtest.py to avoid ↵Daniel Malea2013-08-061-1/+1
| | | | | | | | duplication in the future. - Addresses review comments from Stefanus! llvm-svn: 187816
* Support one more flavour of Intel compiler in TestThreadStepOutDaniel Malea2013-08-061-1/+1
| | | | | | - Thanks to Matt Kopec for noticing the failure! llvm-svn: 187815
* Test compatibility improvements for ICCDaniel Malea2013-08-063-5/+5
| | | | | | | - update TestThreadStepOut.py to work with Intel compilers - fix typo in TestConcurrentEvents llvm-svn: 187801
* Assorted test suite fixes as a result of GCC 4.8 validation effortsDaniel Malea2013-07-301-0/+21
| | | | | | | | | | | | - disable some TestConcurrentEvents cases (which are affected by llvm.org/pr16714 -- watchpoints in multithreaded programs) - relax number-of-bp-locations check in TestUniqueTypes/TestUnsignedTypes - skip TestDataFormatterStdVector cases with GCC 4.8 (known failure due to llvm.org/pr15301) - workaround for race condition in TestHelloWorld.py - update TestSettings.py to work on distros (like Fedora) that have /bin/cat hardlinked to /usr/bin/cat After these changes, the test suite should run cleanly against GCC 4.8 (with DWARF v4)! llvm-svn: 187451
* Fix TestConcurrentEvents to behave nicely with GCC 4.8Daniel Malea2013-07-291-1/+9
| | | | | | | - newer gcc generates additional debuginfo for function exit (stack object desctruction) which was causing tests to fail - work-around consists of not declaring any stack objects in main() llvm-svn: 187389
* tests: Mark expected FreeBSD failures due to pr16706Ed Maste2013-07-251-0/+17
| | | | | | Watchpoints are not yet working on FreeBSD llvm-svn: 187134
OpenPOWER on IntegriCloud