Revision tags: llvmorg-2.9.0-rc1 |
|
#
399f1caf |
| 05-Nov-2010 |
Jim Ingham <jingham@apple.com> |
Added the equivalent of gdb's "unwind-on-signal" to the expression command, and a parameter to control it in ClangUserExpression, and on down to ClangFunction.
llvm-svn: 118290
|
Revision tags: llvmorg-2.8.0 |
|
#
0184f019 |
| 05-Oct-2010 |
Greg Clayton <gclayton@apple.com> |
Moved expression evaluation from CommandObjectExpression into ClangUserExpression::Evaluate () as a public static function so anyone can evaluate an expression.
llvm-svn: 115581
|
Revision tags: llvmorg-2.8.0-rc3 |
|
#
6c68fb45 |
| 30-Sep-2010 |
Jim Ingham <jingham@apple.com> |
Add "-o" option to "expression" which prints the object description if available.
llvm-svn: 115115
|
Revision tags: llvmorg-2.8.0-rc2 |
|
#
a7015092 |
| 18-Sep-2010 |
Greg Clayton <gclayton@apple.com> |
Fixed the way set/show variables were being accessed to being natively accessed by the objects that own the settings. The previous approach wasn't very usable and made for a lot of unnecessary code
Fixed the way set/show variables were being accessed to being natively accessed by the objects that own the settings. The previous approach wasn't very usable and made for a lot of unnecessary code just to access variables that were already owned by the objects.
While I fixed those things, I saw that CommandObject objects should really have a reference to their command interpreter so they can access the terminal with if they want to output usaage. Fixed up all CommandObjects to take an interpreter and cleaned up the API to not need the interpreter to be passed in.
Fixed the disassemble command to output the usage if no options are passed down and arguments are passed (all disassebmle variants take options, there are no "args only").
llvm-svn: 114252
show more ...
|
#
3f4c09c1 |
| 07-Sep-2010 |
Caroline Tice <ctice@apple.com> |
Small help text fixes, to make it more consistent and accurate.
Temporarily remove -l option from 'expr' command (at Sean's request).
llvm-svn: 113298
|
Revision tags: llvmorg-2.8.0-rc1, llvmorg-2.8.0-rc0 |
|
#
fcd43b71 |
| 13-Aug-2010 |
Johnny Chen <johnny.chen@apple.com> |
Modified CommandObjectExpression::EvaluateExpression() so that it takes an additional (ComandReturnObject *) result parameter (default to NULL) and does the right thing in setting the result status.
Modified CommandObjectExpression::EvaluateExpression() so that it takes an additional (ComandReturnObject *) result parameter (default to NULL) and does the right thing in setting the result status.
Also removed used variable ast_context.
llvm-svn: 110992
show more ...
|
#
fc16cc0a |
| 06-Aug-2010 |
Sean Callanan <scallanan@apple.com> |
Removed the -i option from the expr command, and made IR-based expression evaluation the default.
Also added a new class to hold persistent variables. The class is empty as yet while I write up a de
Removed the -i option from the expr command, and made IR-based expression evaluation the default.
Also added a new class to hold persistent variables. The class is empty as yet while I write up a design document for what it will do. Also the place where it is currently created (by the Expression command) is certainly wrong.
llvm-svn: 110415
show more ...
|
#
1d389c4b |
| 23-Jun-2010 |
Sean Callanan <scallanan@apple.com> |
Added the temporary -i option to expr, which switches the expression parsing over to use the LLVM IR as opposed to Clang ASTs. Right now, that functionality only logs.
llvm-svn: 106695
|
#
6611103c |
| 23-Jun-2010 |
Greg Clayton <gclayton@apple.com> |
Very large changes that were needed in order to allow multiple connections to the debugger from GUI windows. Previously there was one global debugger instance that could be accessed that had its own
Very large changes that were needed in order to allow multiple connections to the debugger from GUI windows. Previously there was one global debugger instance that could be accessed that had its own command interpreter and current state (current target/process/thread/frame). When a GUI debugger was attached, if it opened more than one window that each had a console window, there were issues where the last one to setup the global debugger object won and got control of the debugger.
To avoid this we now create instances of the lldb_private::Debugger that each has its own state: - target list for targets the debugger instance owns - current process/thread/frame - its own command interpreter - its own input, output and error file handles to avoid conflicts - its own input reader stack
So now clients should call:
SBDebugger::Initialize(); // (static function)
SBDebugger debugger (SBDebugger::Create()); // Use which ever file handles you wish debugger.SetErrorFileHandle (stderr, false); debugger.SetOutputFileHandle (stdout, false); debugger.SetInputFileHandle (stdin, true);
// main loop SBDebugger::Terminate(); // (static function) SBDebugger::Initialize() and SBDebugger::Terminate() are ref counted to ensure nothing gets destroyed too early when multiple clients might be attached.
Cleaned up the command interpreter and the CommandObject and all subclasses to take more appropriate arguments.
llvm-svn: 106615
show more ...
|
#
40af72e1 |
| 15-Jun-2010 |
Jim Ingham <jingham@apple.com> |
Move Args.{cpp,h} and Options.{cpp,h} to Interpreter where they really belong.
llvm-svn: 106034
|
#
30fdc8d8 |
| 08-Jun-2010 |
Chris Lattner <sabre@nondot.org> |
Initial checkin of lldb code from internal Apple repo.
llvm-svn: 105619
|