6 Commits

Author	SHA1	Message	Date
Greg Clayton	7b0992d9cd	After discussing with Chris Lattner, we require C++11, so lets get rid of the macros and just use C++11. ... llvm-svn: 179805	2013-04-18 22:45:39 +00:00
Greg Clayton	e01e07b6e7	Since we use C++11, we should switch over to using std::unique_ptr when C++11 is being used. To do this, we follow what we have done for shared pointers and we define a STD_UNIQUE_PTR macro that can be used and it will "do the right thing". Due to some API differences in std::unique_ptr and due to the fact that we need to be able to compile without C++11, we can't use move semantics so some code needed to change so that it can compile with either C++. ... Anyone wanting to use a unique_ptr or auto_ptr should now use the "STD_UNIQUE_PTR(TYPE)" macro. llvm-svn: 179779	2013-04-18 18:10:51 +00:00
Jim Ingham	0161b49cba	Reworked the way Process::RunThreadPlan and the ThreadPlanCallFunction interoperate to fix problems where ... hitting auto-continue signals while running a thread plan would cause us to lose control of the debug session. <rdar://problem/12993641> llvm-svn: 174793	2013-02-09 01:29:05 +00:00
Jim Ingham	184e981111	Separated the "expr --unwind-on-error" behavior into two parts, actual errors (i.e. crashes) which continue to be ... controlled by the --unwind-on-error flag, and --ignore-breakpoint which separately controls behavior when a called function hits a breakpoint. For breakpoints, we don't unwind, we either stop, or ignore the breakpoint, which makes more sense. Also make both these behaviors globally settable through "settings set". Also handle the case where a breakpoint command calls code that ends up re-hitting the breakpoint. We were recursing and crashing. Now we just stop without calling the second command. <rdar://problem/12986644> <rdar://problem/9119325> llvm-svn: 172503	2013-01-15 02:47:48 +00:00
Greg Clayton	cced1566e2	API cleanup. ... llvm-svn: 166070	2012-10-16 22:58:25 +00:00
Jim Ingham	35e1bda695	Add the ability to set timeout & "run all threads" options both from the "expr" command and from ... the SB API's that evaluate expressions. <rdar://problem/12457211> llvm-svn: 166062	2012-10-16 21:41:58 +00:00