summaryrefslogtreecommitdiffstats
path: root/lldb/source/Commands/CommandObjectGUI.cpp
Commit message (Collapse)AuthorAgeFilesLines
* Don't #include "lldb-python.h" from anywhere.Zachary Turner2015-05-291-2/+0
| | | | | | | | | | | | | Since interaction with the python interpreter is moving towards being more isolated, we won't be able to include this header from normal files anymore, all includes of it should be localized to the python library which will live under source/bindings/API/Python after a future patch. None of the files that were including this header actually depended on it anyway, so it was just a dead include in every single instance. llvm-svn: 238581
* Typing "gui" will crash programs that don't give LLDB a real terminal. Greg Clayton2015-01-141-4/+16
| | | | | | | | | | We now verify that the debugger's input file is a valid terminal file descriptor before allowing the "gui" command to try to run. Xcode would crash if you typed "gui" at the command line prior to this fix. <rdar://problem/18775851> llvm-svn: 226027
* Fixing the Windows build for the changes brought in from the iohandler merge.Deepak Panickal2014-01-311-0/+5
| | | | llvm-svn: 200565
* Merging the iohandler branch back into main. Greg Clayton2014-01-271-0/+56
The many many benefits include: 1 - Input/Output/Error streams are now handled as real streams not a push style input 2 - auto completion in python embedded interpreter 3 - multi-line input for "script" and "expression" commands now allow you to edit previous/next lines using up and down arrow keys and this makes multi-line input actually a viable thing to use 4 - it is now possible to use curses to drive LLDB (please try the "gui" command) We will need to deal with and fix any buildbot failures and tests and arise now that input/output and error are correctly hooked up in all cases. llvm-svn: 200263
OpenPOWER on IntegriCloud