* progmodes/gdb-mi.el (gdb-running, gdb-starting): Remove

signals for which replies are never received.

diff --git a/lisp/ChangeLog b/lisp/ChangeLog
index d1c27acff24264f02055f8730338276f74a78dec..4207866beb5a7e3c06596a596f2c114074c7482d 100644 (file)
--- a/lisp/ChangeLog
+++ b/lisp/ChangeLog
@@ -1,3 +1,8 @@
+2013-05-14  Jean-Philippe Gravel  <jpgravel@gmail.com>
+
+       * progmodes/gdb-mi.el (gdb-running, gdb-starting): Remove
+       signals for which replies are never received.
+
 2013-05-14  Jean-Philippe Gravel  <jpgravel@gmail.com>
 
        * progmodes/gdb-mi.el: Fix non-responsive gud commands (bug#13845)

diff --git a/lisp/progmodes/gdb-mi.el b/lisp/progmodes/gdb-mi.el
index 2799eecb553f5a9368c9d0836f875ee33f98746e..a6ad57365765f901ffdf2e8f55722076d34b992e 100644 (file)
--- a/lisp/progmodes/gdb-mi.el
+++ b/lisp/progmodes/gdb-mi.el
@@ -2376,8 +2376,7 @@ Sets `gdb-thread-number' to new id."
    (propertize gdb-inferior-status 'face font-lock-type-face))
   (when (not gdb-non-stop)
     (setq gud-running t))
-  (setq gdb-active-process t)
-  (gdb-emit-signal gdb-buf-publisher 'update-threads))
+  (setq gdb-active-process t))
 
 (defun gdb-starting (_output-field _result)
   ;; CLI commands don't emit ^running at the moment so use gdb-running too.
@@ -2385,11 +2384,7 @@ Sets `gdb-thread-number' to new id."
   (gdb-force-mode-line-update
    (propertize gdb-inferior-status 'face font-lock-type-face))
   (setq gdb-active-process t)
-  (setq gud-running t)
-  ;; GDB doesn't seem to respond to -thread-info before first stop or
-  ;; thread exit (even in non-stop mode), so this is useless.
-  ;; Behavior may change in the future.
-  (gdb-emit-signal gdb-buf-publisher 'update-threads))
+  (setq gud-running t))
 
 ;; -break-insert -t didn't give a reason before gdb 6.9