From eb5b45aa6cb44a62b03d9bf1c0d06c0f613bf35f Mon Sep 17 00:00:00 2001 From: Leena Miettinen Date: Mon, 16 Oct 2017 16:53:40 +0200 Subject: [PATCH] Doc: Add tip about stopping processes to troubleshooting debugger A customer had trouble launching debugger on a Wacom Tablet when other processes were running. After all processes were stopped, the debugger could be launched. Change-Id: Ifd3da7904e9ff8e7af958e6abc7b21c1a88fa2e2 Reviewed-by: hjk Reviewed-by: Mika Salmela --- doc/src/debugger/creator-debugger.qdoc | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/doc/src/debugger/creator-debugger.qdoc b/doc/src/debugger/creator-debugger.qdoc index f283e31d245..98b2d2d7bea 100644 --- a/doc/src/debugger/creator-debugger.qdoc +++ b/doc/src/debugger/creator-debugger.qdoc @@ -1537,6 +1537,10 @@ \l{http://www.avira.com/en/support-for-business-knowledgebase-detail/kbid/805} {Restricted Usability of IDE/Debuggers since 2010-12-08}. + On some devices, such as Wacom Tablets, running processes might stop the + debugger from launching. Stop all running processes and then relaunch the + debugger. + \section1 Debugger Does Not Hit Breakpoints You might have created a release build that does not contain debug