| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
|
|
| |
The additional "const" breaks the FreeBSD buildbot, and does not appear
to be due to a LLVM or Clang change. Revert the change while
investigating further.
This reverts revision 206619.
llvm-svn: 206751
|
|
|
|
|
|
| |
on Linux per pr19478.
llvm-svn: 206620
|
|
|
|
| |
llvm-svn: 206619
|
|
|
|
|
|
|
|
| |
Enable data formatters to see-through pointers/references to typedefs
For instance, if Foo is a typedef to Bar, and there is a formatter for any/all of Bar*, Bar&, Bar&&, then Foo*, Foo&, and Foo&& should pick these up if Foo-specific formatters don't exist
llvm-svn: 205939
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
llvm-svn: 205719
|
|
|
|
|
|
|
|
|
| |
These tests started failing on FreeBSD after r205497 "Make the fail
messages"
llvm.org/pr19347
llvm-svn: 205652
|
|
|
|
|
|
|
| |
A breakpoint at the resume address for "continue" is skipped. This is
presumably the root cause for the Linux failure as well.
llvm-svn: 205482
|
|
|
|
|
|
|
|
| |
Clean up the DynamicValueTestCase
Namely, I split off the part of the test that validates child counts to a separate test
llvm-svn: 205450
|
|
|
|
| |
llvm-svn: 205427
|
|
|
|
|
|
| |
pid, as is the case with a forked subprocess. Also a couple of fixes for unit test failures from Todd Fiala.
llvm-svn: 205405
|
|
|
|
| |
llvm-svn: 205381
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
These changes were written by Greg Clayton, Jim Ingham, Jason Molenda.
It builds cleanly against TOT llvm with xcodebuild. I updated the
cmake files by visual inspection but did not try a build. I haven't
built these sources on any non-Mac platforms - I don't think this
patch adds any code that requires darwin, but please let me know if
I missed something.
In debugserver, MachProcess.cpp and MachTask.cpp were renamed to
MachProcess.mm and MachTask.mm as they picked up some new Objective-C
code needed to launch processes when running on iOS.
llvm-svn: 205113
|
|
|
|
|
|
| |
The issue has been fixed by r204745 and r204750
llvm-svn: 204779
|
|
|
|
| |
llvm-svn: 204763
|
|
|
|
|
|
| |
here.. it is going to be some sort of NS-provided String, but let's not bet on the details
llvm-svn: 204761
|
|
|
|
|
|
|
|
|
|
|
| |
Also added 'import sys' on some tests that are using non-standard
unittest2.skipUnless blocks with code that is intended to do things
that we have more specializes @* attributes for. These skip
conditions were failing to execute due to missing import, causing
darwin-only tests to run on Linux regardless. Will file a bug for
that separately.
llvm-svn: 204747
|
|
|
|
| |
llvm-svn: 204718
|
|
|
|
| |
llvm-svn: 204295
|
|
|
|
| |
llvm-svn: 204282
|
|
|
|
| |
llvm-svn: 204281
|
|
|
|
|
|
| |
(<rdar://problem/16363195>).
llvm-svn: 204254
|
|
|
|
| |
llvm-svn: 203993
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
llvm.org/pr19075
llvm-svn: 203245
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
llvm-svn: 202522
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
Failure is not reproducible on ToT LLDB locally or on the buildbot.
llvm.org/pr18313
llvm-svn: 202043
|
|
|
|
|
|
| |
llvm.org/pr17232
llvm-svn: 201928
|
|
|
|
|
|
|
|
| |
And add a decorator for llvm.org/pr18200
Patch by John Wolfe.
llvm-svn: 201708
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
llvm.org/pr18832
llvm-svn: 201705
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
llvm.org/pr18832
Reported by John Wolfe
llvm-svn: 201418
|
|
|
|
|
|
| |
See http://llvm.org/bugs/show_bug.cgi?id=18816.
llvm-svn: 201357
|
|
|
|
|
|
| |
llvm.org/pr18805 fixed by r201270
llvm-svn: 201284
|
|
|
|
| |
llvm-svn: 201270
|
|
|
|
|
|
|
| |
See http://llvm.org/bugs/show_bug.cgi?id=18816.
Likely the same issue as http://llvm.org/bugs/show_bug.cgi?id=18805.
llvm-svn: 201244
|
|
|
|
| |
llvm-svn: 201168
|
|
|
|
| |
llvm-svn: 201167
|
|
|
|
|
|
|
|
| |
The test expects the inferior to have exited, but it is still stopped.
llvm.org/pr18066
llvm-svn: 201166
|
|
|
|
| |
llvm-svn: 201153
|