summaryrefslogtreecommitdiffstats
path: root/lldb
Commit message (Collapse)AuthorAgeFilesLines
...
* Fix detection of teardown hooks that are already bound.Adrian McCarthy2016-01-141-1/+1
| | | | llvm-svn: 257829
* Removed a redundant function call after review.Sean Callanan2016-01-141-2/+0
| | | | llvm-svn: 257818
* Enable the use of modules in the expression parser by default.Sean Callanan2016-01-143-3/+38
| | | | | | | | | | If your program refers to modules (as indicated in DWARF) we will now try to load these modules and give you access to their types in expressions. This used to be gated by a setting ("settings set target.auto-import-clang-modules true") but that setting defaulted to false. Now it defaults to true -- but you can disable it by toggling the setting to false. llvm-svn: 257812
* 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
* Fixed a crasher when dealing with table entries that have blank names.Sean Callanan2016-01-143-0/+15
| | | | | | This can happen with -gmodules tables when an anonymous struct is referred to. llvm-svn: 257786
* [RenderScript] Hook kernel invocation.Aidan Dodds2016-01-142-17/+115
| | | | | | This patch adds a hook to track kernel invocations and to track all script and allocation objects used. llvm-svn: 257772
* Update some XFAILs after the 3.8->3.9 version changeTamas Berghammer2016-01-142-2/+2
| | | | llvm-svn: 257761
* Fix ambiguous resolution of clang::ArrayType/llvm::ArrayType in ClangAstContextEwan Crawford2016-01-141-2/+2
| | | | | | | | | | Both llvm and clang have an ArrayType class, which can cause resolution to fail when llvm headers that are implicitly included name this type. source/Symbol/ClangASTContext.cpp has 'using namespace llvm;' and 'using namespace clang;' Author: Luke Drummond <luke.drummond@codeplay.com> Differential Revision: http://reviews.llvm.org/D16155 llvm-svn: 257759
* XFAIL TestCommandScriptImmediateOutput on LinuxTamas Berghammer2016-01-141-0/+1
| | | | llvm-svn: 257755
* change Xcode test run default to ignore xpass on Xunit outputTodd Fiala2016-01-131-2/+2
| | | | | | | | | | The Green Dragon LLVM builders are starting to parse xunit output on LLDB Xcode builders. By default the XML formatter treats xpass (unexpected successes) as failures. The new flag added ensures we simply ignore those for purposes of xUnit output. LLDB is not currently XPASS clean. llvm-svn: 257717
* Fix -Wformat-pedantic warningHans Wennborg2016-01-131-1/+2
| | | | | | | | | | /work/llvm-3.8/llvm.src/tools/lldb/source/API/SBProcess.cpp:1003:73: error: format specifies type 'void *' but the argument has type 'lldb_private::Event *' [-Werror,-Wformat-pedantic] log->Printf ("SBProcess::%s (event.sp=%p) => %d", __FUNCTION__, event.get(), ret_val); ~~ ^~~~~~~~~~~ 1 error generated. llvm-svn: 257692
* Include IR/DerivedTypes.h instead of IR/Type.h to match LLVM change r256406.Hans Wennborg2016-01-131-1/+1
| | | | | | | | | | | | | | | | | | This is similar to r256407 and fixes the following warning: In file included from /work/llvm-3.8/llvm.src/tools/lldb/source/Target/ThreadPlanCallFunctionUsingABI.cpp:14: In file included from /work/llvm-3.8/llvm.src/tools/lldb/include/lldb/Target/ThreadPlanCallFunctionUsingABI.h:23: /work/llvm-3.8/llvm.src/include/llvm/IR/Type.h:350:16: error: inline function 'llvm::Type::getSequentialElementType' is not defined [-Werror,-Wundefined-inline] inline Type *getSequentialElementType() const; ^ /work/llvm-3.8/llvm.src/include/llvm/IR/Type.h:353:46: note: used here Type *getArrayElementType() const { return getSequentialElementType(); } ^ 1 error generated. I'm not sure why it's not showing on any bots. llvm-svn: 257691
* Revert changes to TestProcessLaunch.py as they are breaking a build.Zachary Turner2016-01-132-32/+20
| | | | llvm-svn: 257690
* Rename MSVC top-level folder to avoid name collision.Zachary Turner2016-01-131-1/+1
| | | | | | | | | | | | | | If you have two folders with the same name but different cases, MSBuild gets confused and generates an error when building from within Visual Studio. This patch renames it so that the cases of all folders named "LLDB tests" match. Patch by Jonathan Meier Differential Revision: http://reviews.llvm.org/D16150 llvm-svn: 257684
* Fix some compiler warnings with MSVC 2015.Zachary Turner2016-01-136-3/+8
| | | | llvm-svn: 257671
* Get rid of const char** typemaps.Zachary Turner2016-01-131-70/+7
| | | | | | | | We already have char** typemaps which were near copy-pastes of the const char** versions. This way we have only one version that works for both. llvm-svn: 257670
* Fix TestProcessLaunch for Python 3.Zachary Turner2016-01-134-43/+94
| | | | | | | | | | | | | | | | | | 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
* Fixed a problem where the Xcode build put lldb's __init__.py in the wrong place.Sean Callanan2016-01-131-1/+1
| | | | | | | | | Most of the time CONFIGURATION_BUILD_DIR and BUILT_PRODUCTS_DIR are the same, but they are different in 'xcodebuild install' situations. The file needs to be put into BUILT_PRODUCTS_DIR or lldb's Python interface doesn't work when lldb is built using 'xcodebuild install'. llvm-svn: 257653
* Fix an issue where scripted commands would not actually print any of their ↵Enrico Granata2016-01-137-1/+82
| | | | | | | | output if an immediate output file was set in the result object via a Python file object Fixes rdar://24130303 llvm-svn: 257644
* Silence an incorrect dwarf parsing warningTamas Berghammer2016-01-131-1/+1
| | | | | | | | | | | | We have a check what warns if the offset of a class member is greater then or equal to the size of the class. The warning is valid in most case but it is invalid when the last data member is a 0 size array because in this case the member offset can be equal to the class size (subject to alignment limitations). This CL fixis LLDB to not print out a warning in this special case. llvm-svn: 257603
* [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
* Add a small refinement to the qSymbol:: support in lldb.Jason Molenda2016-01-132-1/+48
| | | | | | | | | | | | | | | This is a packet which allows the remote gdb stub to ask for the address of a symbol in the process. lldb sends the packet (offering to provide addresses for symbol names) after every solib loaded. I changed lldb so that once the stub has indicated that it doesn't need any more symbol addresses, lldb will stop sending the qSymbol:: packet on new solib loads. This can yield a performance benefit over slower communication links when there are many solibs involved. <rdar://problem/23310049> llvm-svn: 257569
* [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 build breakage of r257502.Stephane Sezer2016-01-121-1/+1
| | | | llvm-svn: 257510
* Increase use of svr4 packets to improve performance on POSIX remotesStephane Sezer2016-01-126-145/+361
| | | | | | | | | | | | | | | | | | | | Summary: Allows the remote to enumerate the link map when adding and removing shared libraries, so that lldb doesn't need to read it manually from the remote's memory. This provides very large speedups (on the order of 50%) in total startup time when using the ds2 remote on android or Tizen devices. Reviewers: ADodds, tberghammer, tfiala Subscribers: tberghammer, sas, danalbert, llvm-commits, srhines Differential Revision: http://reviews.llvm.org/D16004 Change by Francis Ricci <fjricci@fb.com> llvm-svn: 257502
* Try to fix the mips64 build after rL257447Tamas Berghammer2016-01-121-1/+1
| | | | llvm-svn: 257469
* Fix for TestNoreturnUnwind.py on i386Ravitheja Addepally2016-01-122-4/+27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* Add clang::Type::Pipe to ClangASTContextPavel Labath2016-01-121-0/+3
| | | | | | | | | | | | | | Summary: Clang recently added support for an OpenCL pipe type. Adding the new type to relevant switches to avoid warnings. Reviewers: clayborg Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D16055 llvm-svn: 257460
* Changes to lldb and debugserver to reduce extraneous memory readsJason Molenda2016-01-1210-65/+285
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | at each public stop to improve performance a bit. Most of the information lldb needed was already in the jThreadsInfo response; complete that information and catch a few cases where we could still fall back to getting the information via discrete memory reads. debugserver adds 'associated_with_dispatch_queue' and 'dispatch_queue_t keys to the jThreadsInfo response for all the threads. lldb needs the dispatch_queue_t value. And associated_with_dispatch_queue helps to identify which threads definitively don't have any queue information so lldb doesn't try to do memory reads to get that information just because it was absent in the jThreadsInfo response. Remove the queue information from the questionmark (T) packet. We'll get the information for all threads via the jThreadsInfo response - sending the information for the stopping thread (on all the private stops, plus the less frequent public stop) was unnecessary information being sent over the wire. SystemRuntimeMacOSX will try to get information about queues by asking the Threads for them, instead of reading memory. ProcessGDBRemote changes to recognize the new keys being sent in the jThreadsInfo response. Changes to ThreadGDBRemote to track the new information. Also, when a thread is marked as definitively not associated with a libdispatch queue, don't fall back to the system runtime to try memory reads to find the queue name / kind / ID etc. <rdar://problem/23309359> llvm-svn: 257453
* [LLDB][MIPS] Fix rL255619: mips 3, 4 and 5 are 64 bit archsMohit K. Bhakkad2016-01-121-3/+3
| | | | llvm-svn: 257448
* [LLDB][MIPS] Fix ReadRegisterValue for registers with constant 32 bit size ↵Mohit K. Bhakkad2016-01-121-1/+9
| | | | | | | | | | regardless of ABI Reviewers: clayborg, tberghammer. Subscribers: jaydeep, bhushan, sagar, nitesh.jain, lldb-commits. Differential Revision: http://reviews.llvm.org/D16060 llvm-svn: 257447
* [LLDB][MIPS] Merge emulation of similar instructions for MIPS64Bhushan D. Attarde2016-01-122-1769/+379
| | | | | | | | | | | SUMMARY: This patch merges emulation of similar instructions into a single function (wherever possible) to remove code duplication. Reviewers: clayborg Subscribers: mohit.bhakkad, sagar, jaydeep, lldb-commits Differential Revision: http://reviews.llvm.org/D16051 llvm-svn: 257442
* [LLDB][MIPS] Handle PIC calling convention for MIPS64Bhushan D. Attarde2016-01-121-0/+8
| | | | | | | | | | | | SUMMARY: This patch sets up register r25 with the address of function to be called in PrepareTrivialCall(). This is required as per MIPS PIC calling convention. Reviewers: clayborg Subscribers: mohit.bhakkad, sagar, jaydeep, lldb-commits Differential Revision: http://reviews.llvm.org/D16046 llvm-svn: 257441
* Get rid of ARM_ELF_SYM_IS_THUMB flag.Stephane Sezer2016-01-121-4/+0
| | | | | | | | | | | | | | Summary: This was used with the old ARM vs. Thumb detection code but is not required anymore. Reviewers: tberghammer, clayborg Subscribers: fjricci, aemerson, lldb-commits, rengolin Differential Revision: http://reviews.llvm.org/D16099 llvm-svn: 257429
* Don't define Bytes and String to be the same number on Py2.Zachary Turner2016-01-111-4/+0
| | | | | | This is causing issues with case labels having the same value. llvm-svn: 257409
* 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
* Fix Python 3 issues related to OS plugins.Zachary Turner2016-01-112-12/+14
| | | | | | | | | | * lldb::tid_t was being converted incorrectly, so this is updated to use PythonInteger instead of manual Python Native API calls. * OSPlugin_RegisterContextData was assuming that the result of get_register_data was a string, when in fact it is a bytes. So this method is updated to use PythonBytes to do the work. llvm-svn: 257398
* Introduce a PythonBytes class into PythonDataObjects.Zachary Turner2016-01-113-0/+166
| | | | | | | This class behaves the same as PythonString on Python2, but differently on Python3. Unittests are added as well. llvm-svn: 257397
* 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-115-172/+172
| | | | | | | | | | | | | | 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
* Don't try to parse the line table when it isn't specifiedTamas Berghammer2016-01-111-6/+11
| | | | | | | | | Previously we tried to parse the line table even if a compile unit had no DW_AT_stmt_list atribute. The problem happens when a compiler generates debug info for a compile unit but doesn't generate any line info. llvm-svn: 257335
* 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
* Make the aarch64 lldb-server capable of debugging arm32 applicationsTamas Berghammer2016-01-114-11/+111
| | | | | | Differential revision: http://reviews.llvm.org/D15533 llvm-svn: 257322
* 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-094-1/+84
| | | | | | | assuming a ValueObject always has a process. So this is that fix and the test case. llvm-svn: 257242
OpenPOWER on IntegriCloud