feedc0de/qt-creator
1
0
Fork 0
forked from qt-creator/qt-creator
Code Pull Requests Activity

Doc: Update examples on how to start debugging from the command line

Browse Source 
Task-number: QTCREATORBUG-9484

Change-Id: Ic5da00c48eb185dc3cd842812e7c36cfefbb6776
Reviewed-by: Orgad Shaneh <orgads@gmail.com>
Reviewed-by: Leena Miettinen <riitta-leena.miettinen@digia.com>
This commit is contained in:
hjk
2013-06-06 14:49:55 +02:00
parent e2a727c450
commit 34261e03cb
2 changed files with 35 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
doc/src/debugger/creator-debugger.qdoc
View File

@@ -726,15 +726,17 @@
attach it to a running process, specify the process ID as a parameter for attach it to a running process, specify the process ID as a parameter for
the \c {-debug} option. To examine a core file, specify the file name. the \c {-debug} option. To examine a core file, specify the file name.
\QC executes all the necessary steps, such as searching for \QC executes all the necessary steps, such as searching for
the binary that belongs to a core file. the binary that belongs to a core file. To connect to a debug server,
specify the server location and port number.
For example: For example:
\list \list
\li \c {C:\qtcreator\bin>qtcreator -debug 2000} \li \c {C:\qtcreator\bin>qtcreator -debug 2000}
\li \c {C:\qtcreator\bin>qtcreator -debug core=core.2000}
\li \c {C:\qtcreator\bin>qtcreator -debug core.2000} \li \c {C:\qtcreator\bin>qtcreator -debug some.exe,core=core}
\li \c {C:\qtcreator\bin>qtcreator -debug server=some.dot.com:4251}
\endlist \endlist

32
doc/src/howto/creator-cli.qdoc
View File

@@ -100,8 +100,36 @@
\li Core plugin: override the selected UI color. \li Core plugin: override the selected UI color.
\row \row
\li -debug <PID-or-corefile> \li -debug <pid>
\li Debugger plugin: attach to process ID or core file. \li Debugger plugin: attach to the process with the given process ID.
\row
\li -debug <executable>[,kit=<kit>]
\li Debugger plugin: launch and debug the executable with the name
\c{executable}.
A \c{kit} can be specified to point to non-default debuggers
and sysroots.
\row
\li -debug [executable,]core=<corefile>[,kit=<kit>]
\li Debugger plugin: load the core file named \c{corefile}.
The parameter \c{executable} specifies the executable that
produced the core file.
If this parameter is omitted, \QC will attempt to reconstruct
it from the core file itself.
This will fail for paths with more than about 80 characters.
In such cases the \c{executable} parameter is mandatory.
A \c{kit} can be specified to point to non-default debuggers
and sysroots.
\row
\li -debug <executable>,server=<server:port>[,kit=<kit>]
\li Debugger plugin: attach to a debug server running on the port
\c{port} on the server \c{server}. The parameter \c{executable}
specifies a local copy of the executable the remote debug server is
manipulating.
A \c{kit} can be specified to point to non-default debuggers
and sysroots.
\row \row
\li -wincrashevent <event-handle> \li -wincrashevent <event-handle>