Debugger: Ignore async GDB notifications while extracting variables

Recent builds of GDB started to deliver *running and *stopped
notifications for expression evaluation, even unpaired at times.
Since we know that we are stopped when we start variable extraction
and we are stopped when it ends, the intermediate notifications
can be ignored.

Change-Id: I800082afb7df600ad4e6f97b534f4ea901c02d8a
Reviewed-by: Christian Stenger <christian.stenger@theqtcompany.com>

src/plugins/debugger/gdb/gdbengine.h

@@ -171,7 +171,9 @@ private: ////////// Gdb Command Management //////////
         // This command needs to be send immediately.
         Immediate = 256,
         // This is a command that needs to be wrapped into -interpreter-exec console
-        ConsoleCommand = 512
+        ConsoleCommand = 512,
+        // This is the UpdateLocals commannd during which we ignore notifications
+        InUpdateLocals = 1024
     };
     Q_DECLARE_FLAGS(GdbCommandFlags, GdbCommandFlag)
 
@@ -432,6 +434,10 @@ protected:
     // For short-circuiting stack and thread list evaluation.
     bool m_stackNeeded;
 
+    // For suppressing processing *stopped and *running responses
+    // while updating locals.
+    bool m_inUpdateLocals;
+
     bool isQFatalBreakpoint(const BreakpointResponseId &id) const;
     bool isHiddenBreakpoint(const BreakpointResponseId &id) const;