aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorLeena Miettinen <riitta-leena.miettinen@digia.com>2013-02-22 14:40:55 +0100
committerLeena Miettinen <riitta-leena.miettinen@digia.com>2013-02-22 15:14:30 +0100
commit88fe1ce5b7dbefcc9c1f577edef009c7398c79ea (patch)
tree4c6758afb52efc9b8a6cde6f543303683106f55a
parentfbbea1b186b0a4c40dae76ea23738d004ac9bd0d (diff)
Doc: new ways of managing breakpoint
Describe breakpoint settings in more detail. Change-Id: I03a9f888fa29c3539f2ed6658f915da5c4c3adc9 Reviewed-by: Leena Miettinen <riitta-leena.miettinen@digia.com>
-rw-r--r--dist/changes-2.7.012
-rw-r--r--doc/images/qtcreator-add-breakpoint.pngbin17638 -> 57327 bytes
-rw-r--r--doc/src/debugger/creator-debugger.qdoc74
3 files changed, 66 insertions, 20 deletions
diff --git a/dist/changes-2.7.0 b/dist/changes-2.7.0
index d6effb07d9..f5869e73d9 100644
--- a/dist/changes-2.7.0
+++ b/dist/changes-2.7.0
@@ -84,16 +84,16 @@ Debugging
types (QByteArray, std::string, char[], char* etc)
* Adjusted to GDB 7.5 changes
* Removed dependency on QmlJSTools
- * Added shortcut to add breakpoint by double click on break view
- * Made breakpoint markers draggable
- * Added logging of exceptions (QTCREATORBUG-8141)
- * Added option to use Intel-style disassembly
- * Improved color highlighting of locals in memory view
+ * Implemented adding breakpoints by double-clicking in Breakpoints view
+ * Implemented dragging and dropping breakpoint markers
+ * Added logging of exceptions in the Compile Output pane (QTCREATORBUG-8141)
+ * Added option to use Intel-style disassembly to debugger GDB options
+ * Improved color highlighting of locals in Memory view
* Made string cutoff value configurable
* Put separate string displays in tab widget (QTCREATORBUG-8344)
* Implemented basic value editing for CDB (QTCREATORBUG-8344)
* Implemented support for displaying images in CDB
- * Added framework to wrap plain GDB pretty printers for use in Creator
+ * Added framework to wrap plain GDB pretty printers for use in Qt Creator
* Implemented display format changes for multi-selection
(QTCREATORBUG-7577)
diff --git a/doc/images/qtcreator-add-breakpoint.png b/doc/images/qtcreator-add-breakpoint.png
index b984afbf96..a21f6b737b 100644
--- a/doc/images/qtcreator-add-breakpoint.png
+++ b/doc/images/qtcreator-add-breakpoint.png
Binary files differ
diff --git a/doc/src/debugger/creator-debugger.qdoc b/doc/src/debugger/creator-debugger.qdoc
index 3083441230..f9429d1ffc 100644
--- a/doc/src/debugger/creator-debugger.qdoc
+++ b/doc/src/debugger/creator-debugger.qdoc
@@ -502,34 +502,80 @@
The interruption of a program by a breakpoint can be restricted with
certain conditions.
- To set a breakpoint at a particular line you want the program to stop,
- click the left margin or press \key F9 (\key F8 for Mac OS X).
+ You can set and delete breakpoints before the program starts running or
+ while it is running under the debugger's control. Breakpoints are saved
+ together with a session.
+
+ \section2 Adding Breakpoints
+
+ To add breakpoints:
+
+ \list 1
+
+ \li Add a new breakpoint in one of the following ways:
+
+ \list
+
+ \li In the code editor, click the left margin or press \key F9
+ (\key F8 for Mac OS X) at a particular line you want the
+ program to stop.
+
+ \li In the \gui Breakpoints view, double-click in the empty
+ part of the view.
+
+ \li In the \gui Breakpoints view, select \gui {Add Breakpoint}
+ in the context menu.
+
+ \endlist
+
+ \li In the \gui {Breakpoint type} field, select the location in the
+ program code where you want the program to stop. The other options
+ to specify depend on the selected location.
- To set breakpoints, select \gui {Add Breakpoint} in
- the context menu in the \gui Breakpoints view.
+ \image qtcreator-add-breakpoint.png "Add Breakpoints" dialog
- \image qtcreator-add-breakpoint.png "Add Breakpoints" dialog
+ \li In the \gui Condition field, set the condition to be evaluated
+ before stopping at the breakpoint if the condition evaluates as
+ true.
- \note You can remove a breakpoint:
+ \li In the \gui Ignore field, specify the number of times that the
+ breakpoint is ignored before the program stops.
+
+ \li In the \gui Commands field, specify the commands to execute when
+ the program stops; one command on a line. GDB executes the commands
+ in the order in which they are specified.
+
+ \endlist
+
+ For more information on breakpoints, see
+ \l{http://sourceware.org/gdb/onlinedocs/gdb/Breakpoints.html#Breakpoints}
+ {Breakpoints, Watchpoints, and Catchpoints} in GDB documentation.
+
+ \section2 Moving Breakpoints
+
+ To move the breakpoint, drag and drop a breakpoint marker to another line.
+
+ \section2 Deleting Breakpoints
+
+ To delete breakpoints:
\list
- \li By clicking the breakpoint marker in the text editor.
+ \li Click the breakpoint marker in the text editor.
- \li By selecting the breakpoint in the breakpoint view and pressing
+ \li Select the breakpoint in the \gui Breakpoints view and press
\key{Delete}.
- \li By selecting \gui{Delete Breakpoint} from the context
- menu in the \gui Breakpoints view.
+ \li Select \gui{Delete Breakpoint} in the context menu in the
+ \gui Breakpoints view.
\endlist
- You can set and delete breakpoints before the program starts running or
- while it is running under the debugger's control. Breakpoints are saved
- together with a session.
-
\section2 Setting Data Breakpoints
+ A \e {data breakpoint} stops the program when data is read or written at the
+ specified address.
+
To set a data breakpoint at an address:
\list 1