summaryrefslogtreecommitdiffstats
path: root/lldb
Commit message (Collapse)AuthorAgeFilesLines
* [LLDB][MIPS] Fix GetUserRegisterInfoCount to count no of regs which are ↵Mohit K. Bhakkad2015-11-034-10/+26
| | | | | | | | | | physically present Reviewers: clayborg, labath. Subscribers: jaydeep, bhushan, sagar, nitesh.jain, lldb-commits. Differential Revision: http://reviews.llvm.org/D13859 llvm-svn: 251906
* [LLDB][Watchpoint] Change ignore_count condition location to fix watchpoint ↵Mohit K. Bhakkad2015-11-032-3/+10
| | | | | | | | | | ignore feature for architectures with watchpoint_exceptions_received=before Reviewers: jingham. Subscribers: clayborg, jaydeep, bhushan, sagar, nitesh.jain, lldb-commits. Differential Revision: http://reviews.llvm.org/D13296 llvm-svn: 251905
* Do not try to copy host memory from address 0Enrico Granata2015-11-031-1/+1
| | | | llvm-svn: 251889
* Add the ability to pass an EvaluateExpressionOptions when you make a ↵Jim Ingham2015-11-0318-30/+72
| | | | | | | | UserExpression. This isn't used in this commit but will be in a future commit. llvm-svn: 251887
* Tighten up sys.path, and use absolute imports everywhere.Zachary Turner2015-11-03414-772/+815
| | | | | | | | | | | | | | | | | | | | For convenience, we had added the folder that dotest.py was in to sys.path, so that we could easily write things like `import lldbutil` from anywhere and any test. This introduces a subtle problem when using Python's package system, because when unittest2 imports a particular test suite, the test suite is detached from the package. Thus, writing "import lldbutil" from dotest imports it as part of the package, and writing the same line from a test does a fresh import since the importing module was not part of the same package. The real way to fix this is to use absolute imports everywhere. Instead of writing "import lldbutil", we need to write "import lldbsuite.test.util". This patch fixes up that and all other similar cases, and additionally removes the script directory from sys.path to ensure that this can't happen again. llvm-svn: 251886
* Emit an error message if the current working directory does not exist when ↵Enrico Granata2015-11-031-1/+7
| | | | | | the user is trying to launch argdumper to do shell expansion llvm-svn: 251882
* Fix usage of removed decorator in TestExpressionsPavel Labath2015-11-031-1/+1
| | | | llvm-svn: 251880
* Provide ADB port forwarding support for abstract sockets.Oleksiy Vyalov2015-11-036-29/+102
| | | | | | http://reviews.llvm.org/D14262 llvm-svn: 251879
* Fix module cache sym links' creation for symbol files.Oleksiy Vyalov2015-11-031-2/+2
| | | | | | http://reviews.llvm.org/D14264 llvm-svn: 251871
* Revert "Make new dotest.py executable"Pavel Labath2015-11-021-0/+0
| | | | | | This was a misunderstanding on my part. The new dotest.py is not meant to be executed directly. llvm-svn: 251863
* Revert "Remove the __import__ hack of lldbtest_config."Pavel Labath2015-11-021-2/+5
| | | | | | The hack still seems to be necessary. Putting it back in until we figure out why. llvm-svn: 251862
* This test case does not actually depend on Cocoa; Foundation is good enoguhEnrico Granata2015-11-022-2/+2
| | | | llvm-svn: 251861
* Create lldbsuite.support package with `seven` file.Zachary Turner2015-11-022-0/+17
| | | | | | | This file will be useful for filling in the gaps where `six` is missing some things we need. llvm-svn: 251847
* Add a sketched out section on adding Language and LanguageRuntime plugins ↵Enrico Granata2015-11-021-0/+23
| | | | | | for language support llvm-svn: 251844
* Revert part of r239007 related to creating the Python symlink.Zachary Turner2015-11-021-9/+0
| | | | | | | | | | | | | | | This has apparently been broken since June, but only on non-Windows. Perhaps nobody noticed it because if the symlink is already there it won't try to re-create it, and nobody ever tried doing a clean build. In any case, I will let the original author attempt to fix this if he is still interested. the problem is that in the normal case of not setting BUILD_SHARED_LIBS and simply running ninja, it would link _lldb.so to a non-existent location, creating a dangling symlink. llvm-svn: 251840
* Change ValueObject::IsLogicalTrue so that it starts by asking the applicable ↵Enrico Granata2015-11-023-0/+26
| | | | | | Language plugin before using the C-style rule llvm-svn: 251838
* Move go expression tests to the new location.Ryan Brown2015-11-022-0/+0
| | | | llvm-svn: 251835
* First pass on www docs: Adding Programming Language Support to LLDBTodd Fiala2015-11-021-0/+170
| | | | | | | We'll hook this up to the main page after Greg, Sean and others iterate on it to a useful point. llvm-svn: 251831
* [dosep] Fix-up callers of process_dir, after it got its argument removedPavel Labath2015-11-021-2/+2
| | | | llvm-svn: 251830
* Calculate size of sockaddr_un manually for abstract sockets:Oleksiy Vyalov2015-11-021-8/+31
| | | | | | | - SUN_LEN doesn't work because strlen(sun_path) == 0 - sizeof(sockaddr_un) doesn't work on Android. llvm-svn: 251825
* Remove the __import__ hack of lldbtest_config.Zachary Turner2015-11-021-5/+2
| | | | | | | | I think the underlying problem was fixed by r251819, but I can't reproduce the problem. So this is to check whether it does in fact fix the problem. llvm-svn: 251822
* Create an expression parser for Go.Ryan Brown2015-11-0229-397/+7215
| | | | | | | | | | | The Go interpreter doesn't JIT or use LLVM, so this also moves all the JIT related code from UserExpression to a new class LLVMUserExpression. Differential Revision: http://reviews.llvm.org/D13073 Fix merge llvm-svn: 251820
* Make dosep correctly invoke the top-level script when forking outZachary Turner2015-11-022-6/+6
| | | | | | | | | | | | | | | | | | | | packages/Python/lldbsuite is now a Python package, and it relies on its __init__.py being called to do package-level initialization. If you exec packages/Python/lldbsuite/dotest.py directly, you won't get this package level initialization, and things will fail. But without this patch, this is exactly what dosep itself does. To launch the multi-processing fork, it was hardcoding a path to dotest.py and exec'ing it from inside the package. The fix here is to get the path of the top-level script, and then exec'ing that instead. A more robust solution would involve refactoring the code so that dosep execs some internal script that imports lldbsuite, but that's a bit more involved. Differential Revision: http://reviews.llvm.org/D14157 Reviewed by: Todd Fiala llvm-svn: 251819
* Handle the options and parameters separator in every MI commandHafiz Abid Qadeer2015-11-025-3/+8
| | | | | | | | | | | | | | | | | | | Summary: As per the following link, the "--" separator can appear between the options and parameters of any MI command. Previously this separator was only handled by the `-data-disassemble` MI command. I have moved the relevant code into `CMICmdBase` so that any MI command can handle the aforementioned separator. https://sourceware.org/gdb/onlinedocs/gdb/GDB_002fMI-Input-Syntax.html#GDB_002fMI-Input-Syntax Reviewers: ki.stfu Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D14197 llvm-svn: 251793
* Fix Clang-tidy modernize-use-nullptr warnings in include/lldb/API and ↵Eugene Zelenko2015-10-319-429/+334
| | | | | | | | source/API; other minor fixes. Other fixes should reduce number of readability-redundant-smartptr-get and readability-implicit-bool-cast. llvm-svn: 251733
* Harden this test case to do the right thing in the face of compiler changesEnrico Granata2015-10-312-2/+8
| | | | llvm-svn: 251732
* Fix Clang-tidy modernize-use-override warnings in include/lldb/Expression, ↵Eugene Zelenko2015-10-317-155/+122
| | | | | | source/Expression and tools/lldb-mi; other minor fixes. llvm-svn: 251730
* Abstract the notion of the truth value of an expression result, for useJim Ingham2015-10-313-9/+37
| | | | | | in breakpoint conditions. llvm-svn: 251727
* Make the error return more explicit when an SBValue has no value.Jim Ingham2015-10-301-0/+3
| | | | llvm-svn: 251722
* Add a few missing includes.Jim Ingham2015-10-301-0/+2
| | | | llvm-svn: 251721
* Fix an error message (the debugger was invalid, not the target.)Jim Ingham2015-10-301-1/+1
| | | | llvm-svn: 251720
* Fix Clang-tidy modernize-use-nullptr warnings in source/Breakpoint; other ↵Eugene Zelenko2015-10-3011-209/+142
| | | | | | minor fixes. llvm-svn: 251716
* Remove 2 lines missed in earlier commit (r251636).Hafiz Abid Qadeer2015-10-301-2/+0
| | | | llvm-svn: 251704
* Mark another TestEvents test as flaky on linuxPavel Labath2015-10-301-0/+1
| | | | | | | I don't think anything has changed recently - the test was always flaky, but only very rarely. Still, it is causing noise in the buildbots. llvm-svn: 251699
* Make new dotest.py executablePavel Labath2015-10-301-0/+0
| | | | llvm-svn: 251684
* Added real editline tests.Todd Fiala2015-10-304-84/+382
| | | | | | | | | These are two simple tests that make sure single line and multiline content are processed and received by Editline.cpp. Fancier tests to come... llvm-svn: 251681
* Some test cases that need the lldbExec path were failing because lldbExec ↵Enrico Granata2015-10-301-1/+4
| | | | | | | | | | was turning out to be None even though it was being validly set by dotest.py It turns out that lldbtest_config was being imported locally to "lldbsuite.test" instead of globally, so when the test cases got individually brought by a global import via __import__ by unittest2, they did not see the lldbtest_config import, and ended up importing a new separate copy of it, with lldbExec unset This is a simple hackaround that brings lldbtest_config to global visibility and makes sure the configuration data is correctly shared llvm-svn: 251678
* Fix Clang-tidy modernize-use-nullptr warnings in ↵Eugene Zelenko2015-10-307-415/+449
| | | | | | source/Plugins/Process/Utility headers; other minor fixes. llvm-svn: 251676
* Fix Clang-tidy modernize-use-nullptr warnings in include/lldb/Symbol; other ↵Eugene Zelenko2015-10-3012-161/+196
| | | | | | minor fixes. llvm-svn: 251673
* Remove two #if0ed regions of code that we were using for an experiment but ↵Enrico Granata2015-10-291-14/+0
| | | | | | don't really want llvm-svn: 251670
* Add a --offset option to memory read that allows one to specify, given a ↵Enrico Granata2015-10-293-2/+24
| | | | | | type, how many sizeof(type) bytes to speak before starting to read memory llvm-svn: 251668
* Do not accept nullptr descriptions as valid summaries to be printedEnrico Granata2015-10-291-2/+7
| | | | llvm-svn: 251663
* Add a --language (-l) option to the formatter delete commands in order to ↵Enrico Granata2015-10-293-25/+100
| | | | | | | | | allow removing formatters from language categories This is slightly harder to test because formatters cannot be added to language categories, so deletions are irreversible (in a debugger run) I plan to add a test case soon, but I need to think about the right approach to obtain one llvm-svn: 251660
* Give the test class it's own name (it was reusing the name from ↵Jim Ingham2015-10-291-1/+1
| | | | | | TestCompletions.py). llvm-svn: 251657
* Fix Clang-tidy modernize-use-nullptr warnings in remaining files in ↵Eugene Zelenko2015-10-2910-203/+177
| | | | | | include/lldb/Target; other minor fixes. llvm-svn: 251648
* Fix Clang-tidy modernize-use-nullptr warnings in some files in ↵Eugene Zelenko2015-10-293-315/+251
| | | | | | include/lldb/Target; other minor fixes. llvm-svn: 251647
* Add an 'internal' kind of summary to support one-off subclasses of ↵Enrico Granata2015-10-292-3/+19
| | | | | | TypeSummaryImpl llvm-svn: 251642
* Better handle the arguments common to all MI commands.Hafiz Abid Qadeer2015-10-2920-142/+67
| | | | | | | | | | | | | | | | | | | | | | | | Summary: I observed that eclipse was passing --thread-group for many other commands then we are currently handling. Looking at the MI documentation, the following link states that each MI command accept the --thread and --frame option. Looking at the GDB implementation, it seems that apart from these 2, --thread-group is also handled the same way. https://sourceware.org/gdb/onlinedocs/gdb/Context-management.html#Context-management So instead of handling those arguments in every comamnds, I have moved them into the base class and removed them from elsewhere. Now any command can use these arguments. The patch seems big but most of the changes are mechanical. Reviewers: ki.stfu Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D14177 llvm-svn: 251636
* Fixup lldb-argdumper cmake buildPavel Labath2015-10-291-1/+1
| | | | | | forgot to rename in one spot. llvm-svn: 251628
* Fix flakyness in TestChangeProcessGroupPavel Labath2015-10-291-3/+8
| | | | | | | | | | | The test was verifying that the pid of the child is not equal to its process group by searching for text substrings. This failed in the rare cases when the pid actually *was* a substring of the process group (even though they were not equal). Change the test to use SB API and do proper numeric comparisons. llvm-svn: 251626
OpenPOWER on IntegriCloud