Jim Ingham 3ee12ef26e We were accessing the ModuleList in the target without locking it for tasks like ...

setting breakpoints.  That's dangerous, since while we are setting a breakpoint,
the target might hit the dyld load notification, and start removing modules from
the list.  This change adds a GetMutex accessor to the ModuleList class, and
uses it whenever we are accessing the target's ModuleList (as returned by GetImages().)

<rdar://problem/11552372>

llvm-svn: 157668

2012-05-30 02:19:25 +00:00

..

Breakpoint.cpp

We were accessing the ModuleList in the target without locking it for tasks like

2012-05-30 02:19:25 +00:00

BreakpointID.cpp

…

BreakpointIDList.cpp

…

BreakpointList.cpp

If we notice that a module with a given file path is replaced by another with the same file

2012-05-17 18:38:42 +00:00

BreakpointLocation.cpp

Cleanup - removing the ThreadPlanTestCondition and its helper functions. It is not needed,

2012-05-02 00:23:18 +00:00

BreakpointLocationCollection.cpp

…

BreakpointLocationList.cpp

…

BreakpointOptions.cpp

Jeeze... Remove two unneeded #include's of ThreadPlanTestCondition.h, and replace them with

2012-05-02 00:30:53 +00:00

BreakpointResolver.cpp

…

BreakpointResolverAddress.cpp

…

BreakpointResolverFileLine.cpp

Also push file & line breakpoints past the prologue. Also added a "-K" argument to the relevant

2012-05-22 00:12:20 +00:00

BreakpointResolverFileRegex.cpp

…

BreakpointResolverName.cpp

…

BreakpointSite.cpp

…

BreakpointSiteList.cpp

…

Makefile

…

Stoppoint.cpp

…

StoppointCallbackContext.cpp

…

StoppointLocation.cpp

…

Watchpoint.cpp

Jeeze... Remove two unneeded #include's of ThreadPlanTestCondition.h, and replace them with

2012-05-02 00:30:53 +00:00

WatchpointList.cpp

Don't expose the pthread_mutex_t underlying the Mutex & Mutex::Locker classes.

2012-05-04 23:02:50 +00:00