| #
70b57657 |
| 15-May-2011 |
Greg Clayton <[email protected]> |
Added the ability to get the return value from a ThreadPlanCallFunction thread plan. In order to get the return value, you can call:
void ThreadPlanCallFunction::RequestReturnValue (
Added the ability to get the return value from a ThreadPlanCallFunction thread plan. In order to get the return value, you can call:
void ThreadPlanCallFunction::RequestReturnValue (lldb::ValueSP &return_value_sp); This registers a shared pointer to a return value that will get filled in if everything goes well. After the thread plan is run the return value will be extracted for you.
Added an ifdef to be able to switch between the LLVM MCJIT and the standand JIT. We currently have the standard JIT selected because we have some work to do to get the MCJIT fuctioning properly.
Added the ability to call functions with 6 argument in the x86_64 ABI.
Added the ability for GDBRemoteCommunicationClient to detect if the allocate and deallocate memory packets are supported and to not call allocate memory ("_M") or deallocate ("_m") if we find they aren't supported.
Modified the ProcessGDBRemote::DoAllocateMemory(...) and ProcessGDBRemote::DoDeallocateMemory(...) to be able to deal with the allocate and deallocate memory packets not being supported. If they are not supported, ProcessGDBRemote will switch to calling "mmap" and "munmap" to allocate and deallocate memory instead using our trivial function call support.
Modified the "void ProcessGDBRemote::DidLaunchOrAttach()" to correctly ignore the qHostInfo triple information if any was specified in the target. Currently if the target only specifies an architecture when creating the target:
(lldb) target create --arch i386 a.out
Then the vendor, os and environemnt will be adopted by the target.
If the target was created with any triple that specifies more than the arch:
(lldb) target create --arch i386-unknown-unknown a.out
Then the target will maintain its triple and not adopt any new values. This can be used to help force bare board debugging where the dynamic loader for static files will get used and users can then use "target modules load ..." to set addressses for any files that are desired.
Added back some convenience functions to the lldb_private::RegisterContext class for writing registers with unsigned values. Also made all RegisterContext constructors explicit to make sure we know when an integer is being converted to a RegisterValue.
llvm-svn: 131370
show more ...
|
| #
2a48f525 |
| 14-May-2011 |
Greg Clayton <[email protected]> |
Expand the ABI prepare trivial function call to allow 6 simple args.
llvm-svn: 131334
|
| #
fdeb1563 |
| 12-May-2011 |
Greg Clayton <[email protected]> |
Cleaned up the ABI::PrepareTrivialCall() function to take three argument pointers:
virtual bool PrepareTrivialCall (Thread &thread, lldb::addr_t sp,
Cleaned up the ABI::PrepareTrivialCall() function to take three argument pointers:
virtual bool PrepareTrivialCall (Thread &thread, lldb::addr_t sp, lldb::addr_t functionAddress, lldb::addr_t returnAddress, lldb::addr_t *arg1_ptr, lldb::addr_t *arg2_ptr, lldb::addr_t *arg3_ptr) const = 0;
Prior to this it was:
virtual bool PrepareTrivialCall (Thread &thread, lldb::addr_t sp, lldb::addr_t functionAddress, lldb::addr_t returnAddress, lldb::addr_t arg, lldb::addr_t *this_arg, lldb::addr_t *cmd_arg) const = 0;
This was because the function that called this slowly added more features to be able to call a C++ member function that might have a "this" pointer, and then later added "self + cmd" support for objective C. Cleaning this code up and the code that calls it makes it easier to implement the functions for new targets.
The MacOSX_arm::PrepareTrivialCall() is now filled in and ready for testing.
llvm-svn: 131221
show more ...
|
| #
31f1d2f5 |
| 11-May-2011 |
Greg Clayton <[email protected]> |
Moved all code from ArchDefaultUnwindPlan and ArchVolatileRegs into their respective ABI plugins as they were plug-ins that supplied ABI specfic info.
Also hookep up the UnwindAssemblyInstEmulation
Moved all code from ArchDefaultUnwindPlan and ArchVolatileRegs into their respective ABI plugins as they were plug-ins that supplied ABI specfic info.
Also hookep up the UnwindAssemblyInstEmulation so that it can generate the unwind plans for ARM.
Changed the way ABI plug-ins are handed out when you get an instance from the plug-in manager. They used to return pointers that would be mananged individually by each client that requested them, but now they are handed out as shared pointers since there is no state in the ABI objects, they can be shared.
llvm-svn: 131193
show more ...
|
| #
e359d9b7 |
| 09-May-2011 |
Sean Callanan <[email protected]> |
Fixed a bug in which expression-local variables were treated as being permanently resident in target memory. In fact, since the expression's stack frame is deleted and potentially re-used after the
Fixed a bug in which expression-local variables were treated as being permanently resident in target memory. In fact, since the expression's stack frame is deleted and potentially re-used after the expression completes, the variables need to be treated as being freeze-dried.
llvm-svn: 131104
show more ...
|
|
Revision tags: llvmorg-2.9.0, llvmorg-2.9.0-rc3, llvmorg-2.9.0-rc2, llvmorg-2.9.0-rc1 |
|
| #
672e6f59 |
| 07-Mar-2011 |
Jim Ingham <[email protected]> |
Add a method "GetEntryPoint" to the ObjectFile class, and implement it on MachO & ELF - though the ELF implementation is probably a little weak. Then use this method in place of directly looking for
Add a method "GetEntryPoint" to the ObjectFile class, and implement it on MachO & ELF - though the ELF implementation is probably a little weak. Then use this method in place of directly looking for "start" in the ThreadPlanCallFunction constructor to find the stopping point for our function evaluation.
llvm-svn: 127194
show more ...
|
| #
2c36439c |
| 26-Jan-2011 |
Jim Ingham <[email protected]> |
Make sure that if a CallFunction thread plan crashes while running in the "run to address" mode, and it is an auto-discard thread plan, the plan stack unwinds properly.
llvm-svn: 124306
|
| #
9da3683c |
| 22-Jan-2011 |
Jim Ingham <[email protected]> |
Centralize the register reporting (might want to move this function to Thread). Make sure DoTakedown gets called only once by adding a dedicated m_takedown_done bool. Add a little more useful loggin
Centralize the register reporting (might want to move this function to Thread). Make sure DoTakedown gets called only once by adding a dedicated m_takedown_done bool. Add a little more useful logging.
llvm-svn: 124015
show more ...
|
| #
77787033 |
| 20-Jan-2011 |
Jim Ingham <[email protected]> |
Back up both the register AND the stop state when calling functions. Set the thread state to "bland" before calling functions so they don't inherit the pending signals and die.
llvm-svn: 123869
|
| #
bda4e5eb |
| 18-Jan-2011 |
Jim Ingham <[email protected]> |
In ThreadPlanCallFunction, do the Takedown right when the thread plan gets popped. When the function call is discarded (e.g. when it crashes and discard_on_error is true) the plan gets discarded. Y
In ThreadPlanCallFunction, do the Takedown right when the thread plan gets popped. When the function call is discarded (e.g. when it crashes and discard_on_error is true) the plan gets discarded. You need to make sure that the stack gets restored right then, and not wait till you start again and the thread plan stack is cleared.
llvm-svn: 123716
show more ...
|
| #
5ccbd294 |
| 06-Jan-2011 |
Greg Clayton <[email protected]> |
Fixed issues with RegisterContext classes and the subclasses. There was an issue with the way the UnwindLLDB was handing out RegisterContexts: it was making shared pointers to register contexts and t
Fixed issues with RegisterContext classes and the subclasses. There was an issue with the way the UnwindLLDB was handing out RegisterContexts: it was making shared pointers to register contexts and then handing out just the pointers (which would get put into shared pointers in the thread and stack frame classes) and cause double free issues. MallocScribble helped to find these issues after I did some other cleanup. To help avoid any RegisterContext issue in the future, all code that deals with them now returns shared pointers to the register contexts so we don't end up with multiple deletions. Also now that the RegisterContext class doesn't require a stack frame, we patched a memory leak where a StackFrame object was being created and leaked.
Made the RegisterContext class not have a pointer to a StackFrame object as one register context class can be used for N inlined stack frames so there is not a 1 - 1 mapping. Updates the ExecutionContextScope part of the RegisterContext class to never return a stack frame to indicate this when it is asked to recreate the execution context. Now register contexts point to the concrete frame using a concrete frame index. Concrete frames are all of the frames that are actually formed on the stack of a thread. These concrete frames can be turned into one or more user visible frames due to inlining. Each inlined stack frame has the exact same register context (shared via shared pointers) as any parent inlined stack frames all the way up to the concrete frame itself.
So now the stack frames and the register contexts should behave much better.
llvm-svn: 122976
show more ...
|
| #
17827830 |
| 13-Dec-2010 |
Sean Callanan <[email protected]> |
Added support for generating expressions that have access to the members of the Objective-C self object.
The approach we take is to generate the method as a @category on top of the self object, and
Added support for generating expressions that have access to the members of the Objective-C self object.
The approach we take is to generate the method as a @category on top of the self object, and to pass the "self" pointer to it. (_cmd is currently NULL.)
Most changes are in ClangExpressionDeclMap, but the change that adds support to the ABIs to pass _cmd touches a fair amount of code.
llvm-svn: 121722
show more ...
|
| #
36695cde |
| 12-Nov-2010 |
Sean Callanan <[email protected]> |
Excised a version of the low-level function calling logic that supported calling functions with arbitrary arguments. We use ClangFunction for this, and the low-level logic is only required to suppor
Excised a version of the low-level function calling logic that supported calling functions with arbitrary arguments. We use ClangFunction for this, and the low-level logic is only required to support one or two pointer arguments.
llvm-svn: 118871
show more ...
|
| #
06e827cc |
| 11-Nov-2010 |
Jim Ingham <[email protected]> |
Add ThreadPlanTracer class to allow instruction step tracing of execution. Also changed eSetVarTypeBool to eSetVarTypeBoolean to make it consistent with eArgTypeBoolean.
llvm-svn: 118824
|
| #
ece96492 |
| 08-Nov-2010 |
Sean Callanan <[email protected]> |
Added more logging so we see the register state when a function starts and ends, and also the disassembly for anything that is a client of ClangExpressionParser after it has been JIT compiled.
llvm
Added more logging so we see the register state when a function starts and ends, and also the disassembly for anything that is a client of ClangExpressionParser after it has been JIT compiled.
llvm-svn: 118401
show more ...
|
| #
2d4edfbc |
| 06-Nov-2010 |
Greg Clayton <[email protected]> |
Modified all logging calls to hand out shared pointers to make sure we don't crash if we disable logging when some code already has a copy of the logger. Prior to this fix, logs were handed out as po
Modified all logging calls to hand out shared pointers to make sure we don't crash if we disable logging when some code already has a copy of the logger. Prior to this fix, logs were handed out as pointers and if they were held onto while a log got disabled, then it could cause a crash. Now all logs are handed out as shared pointers so this problem shouldn't happen anymore. We are also using our new shared pointers that put the shared pointer count and the object into the same allocation for a tad better performance.
llvm-svn: 118319
show more ...
|
| #
10af7c43 |
| 04-Nov-2010 |
Sean Callanan <[email protected]> |
Re-enabled LLDB's pointer checkers, and moved the implementation of the Objective-C object checkers into the Objective-C language runtime.
llvm-svn: 118226
|
| #
f211510f |
| 03-Nov-2010 |
Sean Callanan <[email protected]> |
Factored the code that implements breakpoints on exceptions for different languages out of ThreadPlanCallFunction and put it into the appropriate language runtimes.
llvm-svn: 118200
|
| #
c98aca60 |
| 03-Nov-2010 |
Sean Callanan <[email protected]> |
Modified ThreadPlanCallFunction to perform the exception checks at the right time, and modified ClangFunction so that it doesn't misinterpret the stop as a timeout stop.
llvm-svn: 118189
|
| #
6db73ca5 |
| 03-Nov-2010 |
Sean Callanan <[email protected]> |
Modified the thread plan that calls functions to set breakpoints at the different locations where an exception could be thrown, so that exceptions thrown by expressions are properly caught.
llvm-svn
Modified the thread plan that calls functions to set breakpoints at the different locations where an exception could be thrown, so that exceptions thrown by expressions are properly caught.
llvm-svn: 118142
show more ...
|
| #
be3a1b14 |
| 26-Oct-2010 |
Sean Callanan <[email protected]> |
Fixed a problem where function calls on i386 weren't being generated correctly.
Also added a messy way to single-step through expressions that I will improve soon.
llvm-svn: 117342
|
| #
40d871fa |
| 26-Oct-2010 |
Jim Ingham <[email protected]> |
The call function thread plan should allow internal breakpoints to continue on. Also made stopping in mid-expression evaluation when we hit a breakpoint/signal work.
llvm-svn: 117341
|
| #
49249493 |
| 19-Oct-2010 |
Sean Callanan <[email protected]> |
Removed a bit of dead code. Thanks to Eric Christopher for pointing it out.
llvm-svn: 116871
|
| #
3e6fedca |
| 19-Oct-2010 |
Sean Callanan <[email protected]> |
Expressions now claim responsibility for all stops that occur while they run. This means that they clean up after themselves even when they crash.
llvm-svn: 116870
|
|
Revision tags: llvmorg-2.8.0, llvmorg-2.8.0-rc3 |
|
| #
fc55f5d1 |
| 21-Sep-2010 |
Sean Callanan <[email protected]> |
Removed the hacky "#define this ___clang_this" handler for C++ classes. Replaced it with a less hacky approach:
- If an expression is defined in the context of a method of class A, then that ex
Removed the hacky "#define this ___clang_this" handler for C++ classes. Replaced it with a less hacky approach:
- If an expression is defined in the context of a method of class A, then that expression is wrapped as ___clang_class::___clang_expr(void*) { ... } instead of ___clang_expr(void*) { ... }.
- ___clang_class is resolved as the type of the target of the "this" pointer in the method the expression is defined in.
- When reporting the type of ___clang_class, a method with the signature ___clang_expr(void*) is added to that class, so that Clang doesn't complain about a method being defined without a corresponding declaration.
- Whenever the expression gets called, "this" gets looked up, type-checked, and then passed in as the first argument.
This required the following changes:
- The ABIs were changed to support passing of the "this" pointer as part of trivial calls.
- ThreadPlanCallFunction and ClangFunction were changed to support passing of an optional "this" pointer.
- ClangUserExpression was extended to perform the wrapping described above.
- ClangASTSource was changed to revert the changes required by the hack.
- ClangExpressionParser, IRForTarget, and ClangExpressionDeclMap were changed to handle different manglings of ___clang_expr flexibly. This meant no longer searching for a function called ___clang_expr, but rather looking for a function whose name *contains* ___clang_expr.
- ClangExpressionParser and ClangExpressionDeclMap now remember whether "this" is required, and know how to look it up as necessary.
A few inheritance bugs remain, and I'm trying to resolve these. But it is now possible to use "this" as well as refer implicitly to member variables, when in the proper context.
llvm-svn: 114384
show more ...
|