comparison lisp/progmodes/gdb-ui.el @ 69234:67e921172c0d

(gdb-speedbar-refresh): Quieten speedbar-refresh.

69233:4ec5a067baf3

;; and compiling with -DUNBUFFERED while debugging.

;;; Known Bugs:

;; 1) Strings that are watched don't update in the speedbar when their
;; contents change.
;; 2) Cannot handle multiple debug sessions.

;;; Problems with watch expressions:

;; 1) They go out of scope when the inferior is re-run.
;; 2) -var-update reports that an out of scope variable has changed:
;;    changelist=[{name="var1",in_scope="false"}], but the value can't be accessed.
;;    (-var-list-children, in contrast allows you to create variable objects of
;;      the children when they are out of scope and get their values).
;; 3) VARNUM increments even when vaiable object is not created (maybe trivial).

;;; TODO:

;; 1) Use MI command -data-read-memory for memory window.
;; 2) Use tree-widget.el instead of the speedbar for watch-expressions?

(defun gdb-speedbar-refresh ()
  (setq gdb-pending-triggers
	(delq 'gdb-speedbar-refresh gdb-pending-triggers))
  (with-current-buffer gud-comint-buffer
    (speedbar-refresh)))

(defun gdb-var-delete ()
  "Delete watch expression at point from the speedbar."
  (interactive)
  (if (memq (buffer-local-value 'gud-minor-mode gud-comint-buffer)

(defun gdb-post-prompt (ignored)
  "An annotation handler for `post-prompt'.
This begins the collection of output from the current command if that
happens to be appropriate."
  ;; Don't add to queue if there outstanding items or GDB is not known yet.
  (unless (or gdb-pending-triggers gdb-first-post-prompt)
    (gdb-get-selected-frame)
    (gdb-invalidate-frames)
    ;; Regenerate breakpoints buffer in case it has been inadvertantly deleted.
    (gdb-get-buffer-create 'gdb-breakpoints-buffer)

69234:67e921172c0d

;; and compiling with -DUNBUFFERED while debugging.

;;; Known Bugs:

;; 1) Strings that are watched don't update in the speedbar when their
;; contents change unless the first character changes.
;; 2) Cannot handle multiple debug sessions.
;; 3) Initially, the assembler buffer does not display the cursor at the
;; current line if the line is not visible in the window (but when testing
;; gdb-assembler-custom with a lisp debugger it does!).

;;; Problems with watch expressions, GDB/MI:

;; 1) They go out of scope when the inferior is re-run.
;; 2) -stack-list-locals has a type field but also prints type in values field.
;; 3) VARNUM increments even when vairable object is not created (maybe trivial).

;;; TODO:

;; 1) Use MI command -data-read-memory for memory window.
;; 2) Use tree-widget.el instead of the speedbar for watch-expressions?

(defun gdb-speedbar-refresh ()
  (setq gdb-pending-triggers
	(delq 'gdb-speedbar-refresh gdb-pending-triggers))
  (with-current-buffer gud-comint-buffer
    (let ((speedbar-verbosity-level 0))
      (save-excursion
	(speedbar-refresh)))))

(defun gdb-var-delete ()
  "Delete watch expression at point from the speedbar."
  (interactive)
  (if (memq (buffer-local-value 'gud-minor-mode gud-comint-buffer)

(defun gdb-post-prompt (ignored)
  "An annotation handler for `post-prompt'.
This begins the collection of output from the current command if that
happens to be appropriate."
  ;; Don't add to queue if there outstanding items or gdb-version is not known
  ;; yet.
  (unless (or gdb-pending-triggers gdb-first-post-prompt)
    (gdb-get-selected-frame)
    (gdb-invalidate-frames)
    ;; Regenerate breakpoints buffer in case it has been inadvertantly deleted.
    (gdb-get-buffer-create 'gdb-breakpoints-buffer)