forked from OSchip/llvm-project
f08f5c9926
You can get a breakpoint to auto-continue by adding "continue" as a command, but that has the disadvantage that if you hit two breakpoints simultaneously, the continue will force the process to continue, and maybe even forstalling the commands on the other. The auto-continue flag means the breakpoints can negotiate about whether to stop. Writing tests, I wanted to supply some commands when I made the breakpoints, so I also added that ability. llvm-svn: 309969 |
||
|---|---|---|
| .. | ||
| Breakpoint.cpp | ||
| BreakpointID.cpp | ||
| BreakpointIDList.cpp | ||
| BreakpointList.cpp | ||
| BreakpointLocation.cpp | ||
| BreakpointLocationCollection.cpp | ||
| BreakpointLocationList.cpp | ||
| BreakpointOptions.cpp | ||
| BreakpointResolver.cpp | ||
| BreakpointResolverAddress.cpp | ||
| BreakpointResolverFileLine.cpp | ||
| BreakpointResolverFileRegex.cpp | ||
| BreakpointResolverName.cpp | ||
| BreakpointSite.cpp | ||
| BreakpointSiteList.cpp | ||
| CMakeLists.txt | ||
| Stoppoint.cpp | ||
| StoppointCallbackContext.cpp | ||
| StoppointLocation.cpp | ||
| Watchpoint.cpp | ||
| WatchpointList.cpp | ||
| WatchpointOptions.cpp | ||