| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary:
- For 'register read --all' command on x86_64-Linux Platform:
-- Provide correct values of X87 FPU Special Purpose Registers
-- Both 32-bit & 64-bit inferiors give correct values on this
Platform
- Added a Test Vector:
-- To verify the expected behaviour of the command
Signed-off-by: Abhishek Aggarwal <abhishek.a.aggarwal@intel.com>
Reviewers: ashok.thirumurthi, granata.enrico, tfiala, clayborg
Differential Revision: http://reviews.llvm.org/D12592
llvm-svn: 246955
|
|
|
|
|
|
|
|
|
|
| |
Reviewers: chaoren
Subscribers: lldb-commits
Differential Revision: http://reviews.llvm.org/D12653
llvm-svn: 246894
|
|
|
|
|
|
| |
people to turn on and off formatters for a given language
llvm-svn: 246884
|
|
|
|
| |
llvm-svn: 246873
|
|
|
|
|
|
|
|
| |
antimalware is holding the handle to the just-created file.
Differential Revision: http://reviews.llvm.org/D12641
llvm-svn: 246870
|
|
|
|
| |
llvm-svn: 246845
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Use the frame's context (instead of just the target's) when evaluating,
so that the language of the frame's CU can be used to select the
compiler and/or compiler options to use when parsing the expression.
This allows for modules built with mixed languages to be parsed in
the context of their frame.
* Add all C and C++ language variants when determining the language options
to set.
* Enable C++ language options when language is C or ObjC as a workaround since
the expression parser uses features of C++ to capture values.
* Enable ObjC language options when language is C++ as a workaround for ObjC
requirements.
* Disable C++11 language options when language is C++03.
* Add test TestMixedLanguages.py to check that the language being used
for evaluation is that of the frame.
* Fix test TestExprOptions.py to check for C++11 instead of C++ since C++ has
to be enabled for C, and remove redundant expr --language test for ObjC.
* Fix TestPersistentPtrUpdate.py to not require C++11 in C.
Reviewed by: clayborg, spyffe, jingham
Subscribers: lldb-commits
Differential Revision: http://reviews.llvm.org/D11102
llvm-svn: 246829
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary:
Remove expected failure decorators from tests which now should start
passing.
Reviewers: clayborg, spyffe
Subscribers: lldb-commits
Differential Revision: http://reviews.llvm.org/D12613
llvm-svn: 246820
|
|
|
|
| |
llvm-svn: 246816
|
|
|
|
|
|
|
| |
See the following for details:
http://reviews.llvm.org/D12587
llvm-svn: 246794
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary: - send empty line for multiple commands to complete
Reviewers: tberghammer
Subscribers: lldb-commits
Differential Revision: http://reviews.llvm.org/D12584
llvm-svn: 246791
|
|
|
|
| |
llvm-svn: 246783
|
|
|
|
|
|
|
| |
There is a more race condition regarding process detach, which this test exposes, marking as
flaky until it is fixed.
llvm-svn: 246777
|
|
|
|
|
|
| |
the test is hitting an assertion in clang.
llvm-svn: 246766
|
|
|
|
|
|
| |
it has been consistently passing at least the last 100 builds on the bot.
llvm-svn: 246761
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary:
There was a race condition in the AsyncThread, where we would end up sending a vAttach
notification to the thread before it got a chance set up its listener (this can be reproduced by
adding a sleep() at the very beginning of ProcessGDBRemote::AsyncThread()). This event would then
get lost and we LLDB would deadlock. I fix this by setting up the listener early on, in the
ProcessGDBRemote constructor.
This should improve the stability of all attach tests. For now, I am removing XTIMEOUT from
TestAttachResume, and will watch the buildbots for signs of trouble.
Reviewers: clayborg, ovyalov
Subscribers: lldb-commits
Differential Revision: http://reviews.llvm.org/D12552
llvm-svn: 246756
|
|
|
|
| |
llvm-svn: 246726
|
|
|
|
|
|
| |
llvm.org/pr24446
llvm-svn: 246725
|
|
|
|
|
|
| |
llvm.org/pr24663
llvm-svn: 246724
|
|
|
|
|
|
|
|
|
| |
On Windows we have to deal with OS created threads, so we can never
know the exact number of threads.
llvm.org/pr24681
llvm-svn: 246723
|
|
|
|
|
|
|
|
|
|
| |
Instead of fixing these tests by finding a pexpect replacement,
this set of tests can be fixed by re-writing the test to not use
pexpect.
llvm.org/pr24679
llvm-svn: 246671
|
|
|
|
|
|
| |
llvm.org/pr24668
llvm-svn: 246670
|
|
|
|
| |
llvm-svn: 246669
|
|
|
|
|
|
| |
https://llvm.org/pr24660
llvm-svn: 246668
|
|
|
|
|
|
| |
tests have been reliably passing at least the last 100 runs of the build bot.
llvm-svn: 246647
|
|
|
|
| |
llvm-svn: 246644
|
|
|
|
|
|
|
|
|
|
|
| |
If a command argument contains a space then it have to be escaped with
backslash signs so the argument parsing logic can parse it properly.
This CL fixes the tab completion code for the arguments to create
complitions with correctly escaped strings.
Differential revision: http://reviews.llvm.org/D12531
llvm-svn: 246639
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary:
The test (among other things) attempts to verify that detaching works while the inferior is
running. However, this was racy since the inferior could end up stopping again before we got a
chance to detach from it (the test could be made to fail reliably by inserting a sleep just after
the last "continue" command). The reason for the stop was that we had a breakpoint set in a place
that can be hit by multiple threads, and we stop because another thread hit a breakpoint.
I fix this by moving the breakpoint to a place that is reachable from only one thread. I also
make sure that the same thread cannot hit the breakpoint if we are exceptionaly slow by flipping
a flag which makes the breakpoint unreachable (I cannot just disable or delete the breakpoint as
the test makes it a point to try detaching while breakpoints are still set).
Another source or racyness was that the test verified that the process resumes and
stops after a "continue". However, if these two events happened too fast, the initial start event
would be lost, and the test would end up confused. I have implemented this in a safer manner and
made a utility function out of it, as I know of a couple of other tests which need the same
functionality.
Reviewers: zturner, clayborg
Subscribers: lldb-commits
Differential Revision: http://reviews.llvm.org/D12527
llvm-svn: 246623
|
|
|
|
| |
llvm-svn: 246570
|
|
|
|
|
|
| |
https://llvm.org/pr24600
llvm-svn: 246569
|
|
|
|
|
|
|
|
|
|
| |
These tests work when run locally. They had been occasionally failing
on the FreeBSD buildbot due to pexpect issues. That buildbot is
currently down, and I expect the replacement will not have this issue.
llvm.org/pr22784
llvm-svn: 246490
|
|
|
|
|
|
|
| |
Just because one test fails to clean up correctly, it should not
prevent other tests from attempting to run.
llvm-svn: 246063
|
|
|
|
|
|
|
| |
This is a nasty hack to work around the issue described in
https://llvm.org/pr24589
llvm-svn: 246062
|
|
|
|
|
|
| |
Fixing this is tracked by https://llvm.org/pr24579
llvm-svn: 246061
|
|
|
|
| |
llvm-svn: 246060
|
|
|
|
|
|
|
|
|
|
|
|
| |
This test runs fine on its own, but leaves python in a bad state to
where all tests that run after it error out. See llvm.org/pr24575.
This resolves the concerns raised in http://reviews.llvm.org/rL237053.
Reviewed by: clayborg, ted
Subscribers: lldb-commits
Differential Revision: http://reviews.llvm.org/D12329
llvm-svn: 246043
|
|
|
|
|
|
| |
in them to more meaningful names
llvm-svn: 245993
|
|
|
|
|
|
|
|
| |
A couple of edge cases are broken with regards to quote handling.
Fixing this is tracked by http://llvm.org/pr24557
llvm-svn: 245984
|
|
|
|
| |
llvm-svn: 245983
|
|
|
|
|
|
| |
apparently, just placing the file under linux/ does not make the test linux specific. :)
llvm-svn: 245848
|
|
|
|
| |
llvm-svn: 245842
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary:
There were a number of issues about the way I have designed this test originally:
- it relied on single-stepping through large parts of code, which was slow and unreliable
- the threading libraries interfered with the exact thing we wanted to test
For this reason, I have rewritted the test using low-level linux api, which allows the test to be
much more focused. The functionality for other platforms will need to be tested separately.
Reviewers: tberghammer
Subscribers: tberghammer, danalbert, srhines, lldb-commits
Differential Revision: http://reviews.llvm.org/D12280
llvm-svn: 245838
|
|
|
|
| |
llvm-svn: 245836
|
|
|
|
|
|
| |
This test needs to be ported to c++ threads.
llvm-svn: 245751
|
|
|
|
| |
llvm-svn: 245750
|
|
|
|
| |
llvm-svn: 245749
|
|
|
|
|
|
|
| |
As with every other platform, this test occasionally hangs on
Windows.
llvm-svn: 245748
|
|
|
|
|
|
|
|
|
| |
clang-cl does not yet support C++ exceptions, so these tests will
not even compile.
Re-enabling these tests is tracked by llvm.org/pr24538
llvm-svn: 245747
|
|
|
|
|
|
| |
test times out on the windows->android buildbot (probably due to android emulator being slow)
llvm-svn: 245691
|
|
|
|
| |
llvm-svn: 245687
|