diff options
| author | Robert Griebl <robert.griebl@pelagicore.com> | 2019-06-25 15:55:05 +0200 |
|---|---|---|
| committer | Robert Griebl <robert.griebl@pelagicore.com> | 2019-06-25 15:55:25 +0200 |
| commit | 2400143fb5b977203cbaf7430ae6f0169b493e6b (patch) | |
| tree | 60916c954681d4531a7cb7429a2867b4769daec5 | |
| parent | 73da9f4f29a2cb0a397d442ffb3efa8e0a889fbd (diff) | |
Clarify single-process debuggingv5.13.0_QtAS
Task-number: AUTOSUITE-1054
Change-Id: I05f6b5d2b1be9fb4f10f53565ec104d953b605aa
Reviewed-by: Kavindra Palaraja <kpalaraja@luxoft.com>
Reviewed-by: Vladimir Minenko <vladimir.minenko@pelagicore.com>
| -rw-r--r-- | doc/debugging.qdoc | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/doc/debugging.qdoc b/doc/debugging.qdoc index e6cebc36..c1ecfe05 100644 --- a/doc/debugging.qdoc +++ b/doc/debugging.qdoc @@ -81,7 +81,9 @@ which the application manager runs: \list \li In \b single-process mode, you can start the \c appman binary using any debugging tool directly, for example, \c{gdb --args appman -c config.yaml}. Since everything runs in a single - process, you can't debug applications independently. + process, you can't debug applications separately. Instead, all applications started are loaded + into \b{a single process}, so you can only debug the entire process at once; not each + application independently. \li In \b multi-process mode, you have to distinguish between debugging the application manager itself or the System UI and debugging individual applications: The application manager and |