| 4097bef16c98898ec7eb9c40de8286be2fb30a9d |
|
01-Aug-2013 |
Jason Molenda <jmolenda@apple.com> |
Re-enable fast stepping for arm targets. The issue being worked
around was fixed in llvm commit r186846.
<rdar://problem/14489274>
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@187620 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Target/ThreadPlanStepRange.cpp
|
| bc16b9273326b81dc4aae022389a9f8c3bdca66d |
|
31-Jul-2013 |
Jim Ingham <jingham@apple.com> |
The DisassemblerLLVMC has a retain cycle - the InstructionLLVMC's contained in its instruction
list have a shared pointer back to their DisassemblerLLVMC. This checkin force clears the InstructionList
in all the places we use the DisassemblerSP to stop the leaking for now. I'll go back and fix this
for real when I have time to do so.
<rdar://problem/14581918>
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@187473 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Target/ThreadPlanStepRange.cpp
|
| 27699d7a8ee49499980c2fcb6a690ae85dcb7e93 |
|
19-Jul-2013 |
Jim Ingham <jingham@apple.com> |
Turn off fast stepping for ARM till the MC's MayAffectControlFlow gets more accurate.
rdar://problem/14488761
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@186646 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Target/ThreadPlanStepRange.cpp
|
| 952e9dc874944fcdbbb224f3ec4fc2c859376f64 |
|
28-Mar-2013 |
Greg Clayton <gclayton@apple.com> |
<rdar://problem/13521159>
LLDB is crashing when logging is enabled from lldb-perf-clang. This has to do with the global destructor chain as the process and its threads are being torn down.
All logging channels now make one and only one instance that is kept in a global pointer which is never freed. This guarantees that logging can correctly continue as the process tears itself down.
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@178191 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Target/ThreadPlanStepRange.cpp
|
| 5e0e372e8b95767b0467f31f8d5ce0d394f50ded |
|
13-Mar-2013 |
Jim Ingham <jingham@apple.com> |
Add a target setting (target.use-fast-stepping) to control using the "run to next branch" stepping algorithm.
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@176958 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Target/ThreadPlanStepRange.cpp
|
| 3aaa2c2d1ff6e944d02f3692525c25058b41db21 |
|
13-Mar-2013 |
Jim Ingham <jingham@apple.com> |
The step by running from branch to branch pretty much works with this checkin (at least for x86_64) but is still
turned off, it needs more qualification. If you want to play with it, change the initialization of m_use_fast_step
to true.
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@176923 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Target/ThreadPlanStepRange.cpp
|
| 7d4083837c5a258375fdc185d464b4ed15759a4b |
|
02-Mar-2013 |
Jim Ingham <jingham@apple.com> |
Convert from the C-based LLVM Disassembler shim to the full MC Disassembler API's.
Calculate "can branch" using the MC API's rather than our hand-rolled regex'es.
As extra credit, allow setting the disassembly flavor for x86 based architectures to intel or att.
<rdar://problem/11319574>
<rdar://problem/9329275>
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@176392 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Target/ThreadPlanStepRange.cpp
|
| 090f83176695d86197b0e86b67dee4160ec5003d |
|
26-Jan-2013 |
Jim Ingham <jingham@apple.com> |
Add "target.process.stop-on-shared-library-events" setting, and make it work.
Add the ability to give breakpoints a "kind" string, and have the StopInfoBreakpoint
print that in the brief description if set. Also print the kind - if set - in the breakpoint
listing.
Give kinds to a bunch of the internal breakpoints.
We were deleting the Mac OS X dynamic loader breakpoint as though the id we had stored away was
a breakpoint site ID, but in fact it was a breakpoint id, so we never actually deleted it. Fixed that.
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@173555 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Target/ThreadPlanStepRange.cpp
|
| 5f35a4be95aed0e5b2cb36f7d785bcbfc67284ae |
|
29-Nov-2012 |
Daniel Malea <daniel.malea@intel.com> |
Resolve printf formatting warnings on Linux:
- use macros from inttypes.h for format strings instead of OS-specific types
Patch from Matt Kopec!
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@168945 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Target/ThreadPlanStepRange.cpp
|
| 69f834fc45d92c3edd5350a0a2c090952a981f67 |
|
11-Sep-2012 |
Jim Ingham <jingham@apple.com> |
Shortcut ThreadPlanStepRange::MischiefManaged - if we have pushed new plans and they are not done, then we aren't done either.
<rdar://problem/12259124>
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@163572 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Target/ThreadPlanStepRange.cpp
|
| 88e3de205708f14431559072ca258899b5ac31cc |
|
03-May-2012 |
Jim Ingham <jingham@apple.com> |
Clean up the usage of "MasterPlan" status in ThreadPlans. Only user-initiated plans
should be MasterPlans that want to stay on the plan stack. So make all plans NOT
MasterPlans by default and then have the SB API's and the CommandObjectThread step
commands set this explicitly.
Also added a "clean up" phase to the Thread::ShouldStop so that if plans get stranded
on the stack, we can remove them. This is done by adding an IsPlanStale method to the
thread plans, and if the plan can know that it is no longer relevant, it returns true,
and the plan and its sub-plans will get discarded.
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@156101 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Target/ThreadPlanStepRange.cpp
|
| 707b7a858ce66b15d01177d4a38ff1ccde44f43c |
|
01-May-2012 |
Jim Ingham <jingham@apple.com> |
Fix reporting of stop reasons when the StepOver & StepIn plans stop because of a crash or breakpoint. Added the ability for a plan to say it is done but doesn't want to be the reason for the stop.
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@155927 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Target/ThreadPlanStepRange.cpp
|
| e787c7ea61b1d857b56a0c42a1cf7535115ecbfc |
|
20-Apr-2012 |
Jim Ingham <jingham@apple.com> |
Make sure the "synchronous breakpoint callbacks" get called before the thread plan logic gets invoked, and if they
ask to continue that should short-circuit the thread plans for that thread. Also add a bit more explanation for
how this machinery is supposed to work.
Also pass eExecutionPolicyOnlyWhenNeeded, not eExecutionPolicyAlways when evaluating the expression for breakpoint
conditions.
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@155236 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Target/ThreadPlanStepRange.cpp
|
| b2cf58a817f6c0d15b2077316810c17d9c8ac173 |
|
09-Mar-2012 |
Jim Ingham <jingham@apple.com> |
First stage of implementing step by "run to next branch". Doesn't work yet, is turned off.
<rdar://problem/10975912>
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@152376 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Target/ThreadPlanStepRange.cpp
|
| 0c31d3d3a4a1d00d53346d8a23b0519f47e55d1f |
|
07-Mar-2012 |
Greg Clayton <gclayton@apple.com> |
<rdar://problem/10997402>
This fix really needed to happen as a previous fix I had submitted for
calculating symbol sizes made many symbols appear to have zero size since
the function that was calculating the symbol size was calling another function
that would cause the calculation to happen again. This resulted in some symbols
having zero size when they shouldn't. This could then cause infinite stack
traces and many other side affects.
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@152244 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Target/ThreadPlanStepRange.cpp
|
| 441e3b9e8bed8c67afd5e520966d7ca16579eac4 |
|
01-Mar-2012 |
Jim Ingham <jingham@apple.com> |
Convert the thread plans over from using the stack count to do their logic to using StackID's. This
should be more efficient.
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@151780 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Target/ThreadPlanStepRange.cpp
|
| f4124deeb9532044a38c0774ced872f2709347da |
|
21-Feb-2012 |
Greg Clayton <gclayton@apple.com> |
Thread hardening part 3. Now lldb_private::Thread objects have std::weak_ptr
objects for the backlink to the lldb_private::Process. The issues we were
running into before was someone was holding onto a shared pointer to a
lldb_private::Thread for too long, and the lldb_private::Process parent object
would get destroyed and the lldb_private::Thread had a "Process &m_process"
member which would just treat whatever memory that used to be a Process as a
valid Process. This was mostly happening for lldb_private::StackFrame objects
that had a member like "Thread &m_thread". So this completes the internal
strong/weak changes.
Documented the ExecutionContext and ExecutionContextRef classes so that our
LLDB developers can understand when and where to use ExecutionContext and
ExecutionContextRef objects.
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@151009 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Target/ThreadPlanStepRange.cpp
|
| ad382c523709e86f01bfea27f1991df9afeef2dd |
|
03-Dec-2011 |
Jim Ingham <jingham@apple.com> |
Make the ThreadPlanStepThrough set a backstop breakpoint on the return address from
the function it is being asked to step through, so that even if we get the trampoline
target wrong (for instance) we will still not lose control.
The other fix here is to tighten up the handling of the case where the current plan
doesn't explain the stop, but a plan above us does. In that case, if the plan that
does explain the stop says it is done, we need to clean up the plans below it and
continue on with our processing.
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@145740 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Target/ThreadPlanStepRange.cpp
|
| 76e55f722acc41f6eaf35a7f988090f97b2c82e0 |
|
15-Oct-2011 |
Jim Ingham <jingham@apple.com> |
Make the step range plans capable of supporting multiple ranges. Also make their constructors public, there isn't any good reason why you shouldn't be able to make these plans.
git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@142026 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Target/ThreadPlanStepRange.cpp
|
| 0f4d0f392fbcd4d2a8b06b2f048ad842d92ee834 |
|
23-Sep-2011 |
Jim Ingham <jingham@apple.com> |
If stepping takes us from the line range we were stepping through into the MIDDLE of another line, then continue till we get to the real beginning of a line. This is mostly to work around debug information bugs.
git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@140416 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Target/ThreadPlanStepRange.cpp
|
| 8af1bb72680cb0e90d15341a38f0714f1c16139d |
|
08-Feb-2011 |
Jim Ingham <jingham@apple.com> |
Formatting.
git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@125076 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Target/ThreadPlanStepRange.cpp
|
| 590cce3c99c1a90e76bce9ababe46079bda149c5 |
|
18-Jan-2011 |
Greg Clayton <gclayton@apple.com> |
Fixed incorrect logging printf (patch from Stephen Wilson).
git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@123780 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Target/ThreadPlanStepRange.cpp
|
| 745ac7a5826fe7c392007941a4046bfb1a8dff81 |
|
11-Nov-2010 |
Jim Ingham <jingham@apple.com> |
Add ThreadPlanTracer class to allow instruction step tracing of execution.
Also changed eSetVarTypeBool to eSetVarTypeBoolean to make it consistent with eArgTypeBoolean.
git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@118824 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Target/ThreadPlanStepRange.cpp
|
| e005f2ce03c489ebde9110678a29cbfe8488d5b4 |
|
06-Nov-2010 |
Greg Clayton <gclayton@apple.com> |
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.
git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@118319 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Target/ThreadPlanStepRange.cpp
|
| 6297a3a5c4d8b61f2429f371bdf207043dbca832 |
|
20-Oct-2010 |
Jim Ingham <jingham@apple.com> |
Don't cache the public stop reason, since it can change as plan completion gets processed. That means GetStopReason needs to return a shared pointer, not a pointer to the thread's cached version. Also allow the thread plans to get and set the thread private stop reason - that is usually more appropriate for the logic the thread plans need to do.
git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@116892 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Target/ThreadPlanStepRange.cpp
|
| 0e81b6475a71b32d1edf30a26487c003cc308bf3 |
|
16-Sep-2010 |
Jim Ingham <jingham@apple.com> |
Step past prologues when we step into functions.
git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@114055 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Target/ThreadPlanStepRange.cpp
|
| eea264007bc5fb42c8f3239726a9d28ae42e1b7b |
|
15-Sep-2010 |
Greg Clayton <gclayton@apple.com> |
Moved the section load list up into the target so we can use the target
to symbolicate things without the need for a valid process subclass.
git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@113895 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Target/ThreadPlanStepRange.cpp
|
| 5205f0b6585a127acc6ed210021abb6091220a89 |
|
03-Sep-2010 |
Greg Clayton <gclayton@apple.com> |
Fixed the StackFrame to correctly resolve the StackID's SymbolContextScope.
Added extra logging for stepping.
Fixed an issue where cached stack frame data could be lost between runs when
the thread plans read a stack frame.
git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@112973 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Target/ThreadPlanStepRange.cpp
|
| 643ee7301b5d4b05c321d906bc0d7ff11f571295 |
|
04-Aug-2010 |
Greg Clayton <gclayton@apple.com> |
Abtracted the old "lldb_private::Thread::StopInfo" into an abtract class.
This will allow debugger plug-ins to make any instance of "lldb_private::StopInfo"
that can completely describe any stop reason. It also provides a framework for
doing intelligent things with the stop info at important times in the lifetime
of the inferior.
Examples include the signal stop info in StopInfoUnixSignal. It will check with
the process to see that the current action is for the signal. These actions
include wether to stop for the signal, wether the notify that the signal was
hit, and wether to pass the signal along to the inferior process. The
StopInfoUnixSignal class overrides the "ShouldStop()" method of StopInfo and
this allows the stop info to determine if it should stop at the signal or
continue the process.
StopInfo subclasses must override the following functions:
virtual lldb::StopReason
GetStopReason () const = 0;
virtual const char *
GetDescription () = 0;
StopInfo subclasses can override the following functions:
// If the subclass returns "false", the inferior will resume. The default
// version of this function returns "true" which means the default stop
// info will stop the process. The breakpoint subclass will check if
// the breakpoint wants us to stop by calling any installed callback on
// the breakpoint, and also checking if the breakpoint is for the current
// thread. Signals will check if they should stop based off of the
// UnixSignal settings in the process.
virtual bool
ShouldStop (Event *event_ptr);
// Sublasses can state if they want to notify the debugger when "ShouldStop"
// returns false. This would be handy for breakpoints where you want to
// log information and continue and is also used by the signal stop info
// to notify that a signal was received (after it checks with the process
// signal settings).
virtual bool
ShouldNotify (Event *event_ptr)
{
return false;
}
// Allow subclasses to do something intelligent right before we resume.
// The signal class will figure out if the signal should be propagated
// to the inferior process and pass that along to the debugger plug-ins.
virtual void
WillResume (lldb::StateType resume_state)
{
// By default, don't do anything
}
The support the Mach exceptions was moved into the lldb/source/Plugins/Process/Utility
folder and now doesn't polute the lldb_private::Thread class with platform
specific code.
git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@110184 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Target/ThreadPlanStepRange.cpp
|
| 5b668b5a3437be4066234d08ab99749897ed8d74 |
|
10-Jul-2010 |
Jim Ingham <jingham@apple.com> |
Properly set the PlanKind for the ThreadPlanStepRange derived classes.
git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@108035 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Target/ThreadPlanStepRange.cpp
|
| 54e7afa84d945f9137f9372ecde432f9e1a702fc |
|
09-Jul-2010 |
Greg Clayton <gclayton@apple.com> |
Merged Eli Friedman's linux build changes where he added Makefile files that
enabled LLVM make style building and made this compile LLDB on Mac OS X. We
can now iterate on this to make the build work on both linux and macosx.
git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@108009 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Target/ThreadPlanStepRange.cpp
|
| 5a47e8bcc7277dc3683f2af2aeb9717184e8360c |
|
19-Jun-2010 |
Jim Ingham <jingham@apple.com> |
Two changes in this checkin. Added a ThreadPlanKind so that I can do some reasoning based on the kind of thread plan
without having to use RTTI.
Removed the ThreadPlanContinue and replaced with a ShouldAutoContinue query that serves the same purpose. Having to push
another plan to assert that if there's no other indication the target should continue when this plan is popped was flakey
and error prone. This method is more stable, and fixed problems we were having with thread specific breakpoints.
git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@106378 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Target/ThreadPlanStepRange.cpp
|
| 24943d2ee8bfaa7cf5893e4709143924157a5c1e |
|
08-Jun-2010 |
Chris Lattner <sabre@nondot.org> |
Initial checkin of lldb code from internal Apple repo.
git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@105619 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Target/ThreadPlanStepRange.cpp
|