1 ;;; gud.el --- Grand Unified Debugger mode for gdb, sdb, dbx, or xdb
4 ;; Author: Eric S. Raymond <esr@snark.thyrsus.com>
7 ;; Keywords: unix, tools
9 ;; Copyright (C) 1992, 1993, 1994 Free Software Foundation, Inc.
11 ;; This file is part of GNU Emacs.
13 ;; GNU Emacs is free software; you can redistribute it and/or modify
14 ;; it under the terms of the GNU General Public License as published by
15 ;; the Free Software Foundation; either version 2, or (at your option)
18 ;; GNU Emacs is distributed in the hope that it will be useful,
19 ;; but WITHOUT ANY WARRANTY; without even the implied warranty of
20 ;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
21 ;; GNU General Public License for more details.
23 ;; You should have received a copy of the GNU General Public License
24 ;; along with GNU Emacs; see the file COPYING. If not, write to
25 ;; the Free Software Foundation, 675 Mass Ave, Cambridge, MA 02139, USA.
29 ;; The ancestral gdb.el was by W. Schelter <wfs@rascal.ics.utexas.edu>
30 ;; It was later rewritten by rms. Some ideas were due to Masanobu.
31 ;; Grand Unification (sdb/dbx support) by Eric S. Raymond <esr@thyrsus.com>
32 ;; The overloading code was then rewritten by Barry Warsaw <bwarsaw@cen.com>,
33 ;; who also hacked the mode to use comint.el. Shane Hartman <shane@spr.com>
34 ;; added support for xdb (HPUX debugger). Rick Sladkey <jrs@world.std.com>
35 ;; wrote the GDB command completion code. Dave Love <d.love@dl.ac.uk>
36 ;; added the IRIX kluge and re-implemented the Mips-ish variant.
43 ;; ======================================================================
44 ;; GUD commands must be visible in C buffers visited by GUD
46 (defvar gud-key-prefix
"\C-x\C-a"
47 "Prefix of all GUD commands valid in C buffers.")
49 (global-set-key (concat gud-key-prefix
"\C-l") 'gud-refresh
)
50 (define-key ctl-x-map
" " 'gud-break
) ;; backward compatibility hack
52 ;; ======================================================================
53 ;; the overloading mechanism
55 (defun gud-overload-functions (gud-overload-alist)
56 "Overload functions defined in GUD-OVERLOAD-ALIST.
57 This association list has elements of the form
58 (ORIGINAL-FUNCTION-NAME OVERLOAD-FUNCTION)"
60 (function (lambda (p) (fset (car p
) (symbol-function (cdr p
)))))
63 (defun gud-massage-args (file args
)
64 (error "GUD not properly entered"))
66 (defun gud-marker-filter (str)
67 (error "GUD not properly entered"))
69 (defun gud-find-file (f)
70 (error "GUD not properly entered"))
72 ;; ======================================================================
75 ;; This macro is used below to define some basic debugger interface commands.
76 ;; Of course you may use `gud-def' with any other debugger command, including
79 ;; A macro call like (gud-def FUNC NAME KEY DOC) expands to a form
80 ;; which defines FUNC to send the command NAME to the debugger, gives
81 ;; it the docstring DOC, and binds that function to KEY in the GUD
82 ;; major mode. The function is also bound in the global keymap with the
85 (defmacro gud-def
(func cmd key
&optional doc
)
86 "Define FUNC to be a command sending STR and bound to KEY, with
87 optional doc string DOC. Certain %-escapes in the string arguments
88 are interpreted specially if present. These are:
90 %f name (without directory) of current source file.
91 %d directory of current source file.
92 %l number of current source line
93 %e text of the C lvalue or function-call expression surrounding point.
94 %a text of the hexadecimal address surrounding point
95 %p prefix argument to the command (if any) as a number
97 The `current' source file is the file of the current buffer (if
98 we're in a C file) or the source file current at the last break or
99 step (if we're in the GUD buffer).
100 The `current' line is that of the current buffer (if we're in a
101 source file) or the source line number at the last break or step (if
102 we're in the GUD buffer)."
104 (list 'defun
func '(arg)
107 (list 'gud-call cmd
'arg
))
114 (list 'global-set-key
115 (list 'concat
'gud-key-prefix key
)
116 (list 'quote func
)))))
118 ;; Where gud-display-frame should put the debugging arrow. This is
119 ;; set by the marker-filter, which scans the debugger's output for
120 ;; indications of the current program counter.
121 (defvar gud-last-frame nil
)
123 ;; Used by gud-refresh, which should cause gud-display-frame to redisplay
124 ;; the last frame, even if it's been called before and gud-last-frame has
126 (defvar gud-last-last-frame nil
)
128 ;; All debugger-specific information is collected here.
129 ;; Here's how it works, in case you ever need to add a debugger to the mode.
131 ;; Each entry must define the following at startup:
134 ;; comint-prompt-regexp
135 ;; gud-<name>-massage-args
136 ;; gud-<name>-marker-filter
137 ;; gud-<name>-find-file
139 ;; The job of the massage-args method is to modify the given list of
140 ;; debugger arguments before running the debugger.
142 ;; The job of the marker-filter method is to detect file/line markers in
143 ;; strings and set the global gud-last-frame to indicate what display
144 ;; action (if any) should be triggered by the marker. Note that only
145 ;; whatever the method *returns* is displayed in the buffer; thus, you
146 ;; can filter the debugger's output, interpreting some and passing on
149 ;; The job of the find-file method is to visit and return the buffer indicated
150 ;; by the car of gud-tag-frame. This may be a file name, a tag name, or
153 ;; ======================================================================
156 ;;; History of argument lists passed to gdb.
157 (defvar gud-gdb-history nil
)
159 (defun gud-gdb-massage-args (file args
)
160 (cons "-fullname" (cons file args
)))
162 ;; There's no guarantee that Emacs will hand the filter the entire
163 ;; marker at once; it could be broken up across several strings. We
164 ;; might even receive a big chunk with several markers in it. If we
165 ;; receive a chunk of text which looks like it might contain the
166 ;; beginning of a marker, we save it here between calls to the
168 (defvar gud-marker-acc
"")
169 (make-variable-buffer-local 'gud-marker-acc
)
171 (defun gud-gdb-marker-filter (string)
173 (setq gud-marker-acc
(concat gud-marker-acc string
))
176 ;; Process all the complete markers in this chunk.
177 (while (string-match "\032\032\\([^:\n]*\\):\\([0-9]*\\):.*\n"
181 ;; Extract the frame position from the marker.
183 (cons (substring gud-marker-acc
(match-beginning 1) (match-end 1))
184 (string-to-int (substring gud-marker-acc
188 ;; Append any text before the marker to the output we're going
189 ;; to return - we don't include the marker in this text.
190 output
(concat output
191 (substring gud-marker-acc
0 (match-beginning 0)))
193 ;; Set the accumulator to the remaining text.
194 gud-marker-acc
(substring gud-marker-acc
(match-end 0))))
196 ;; Does the remaining text look like it might end with the
197 ;; beginning of another marker? If it does, then keep it in
198 ;; gud-marker-acc until we receive the rest of it. Since we
199 ;; know the full marker regexp above failed, it's pretty simple to
200 ;; test for marker starts.
201 (if (string-match "\032.*\\'" gud-marker-acc
)
203 ;; Everything before the potential marker start can be output.
204 (setq output
(concat output
(substring gud-marker-acc
205 0 (match-beginning 0))))
207 ;; Everything after, we save, to combine with later input.
209 (substring gud-marker-acc
(match-beginning 0))))
211 (setq output
(concat output gud-marker-acc
)
216 (defun gud-gdb-find-file (f)
217 (find-file-noselect f
))
219 (defvar gdb-minibuffer-local-map nil
220 "Keymap for minibuffer prompting of gdb startup command.")
221 (if gdb-minibuffer-local-map
223 (setq gdb-minibuffer-local-map
(copy-keymap minibuffer-local-map
))
225 gdb-minibuffer-local-map
"\C-i" 'comint-dynamic-complete-filename
))
228 (defun gdb (command-line)
229 "Run gdb on program FILE in buffer *gud-FILE*.
230 The directory containing FILE becomes the initial working directory
231 and source-file directory for your debugger."
233 (list (read-from-minibuffer "Run gdb (like this): "
234 (if (consp gud-gdb-history
)
235 (car gud-gdb-history
)
237 gdb-minibuffer-local-map nil
238 '(gud-gdb-history .
1))))
239 (gud-overload-functions '((gud-massage-args . gud-gdb-massage-args
)
240 (gud-marker-filter . gud-gdb-marker-filter
)
241 (gud-find-file . gud-gdb-find-file
)
244 (gud-common-init command-line
)
246 (gud-def gud-break
"break %f:%l" "\C-b" "Set breakpoint at current line.")
247 (gud-def gud-tbreak
"tbreak %f:%l" "\C-t" "Set breakpoint at current line.")
248 (gud-def gud-remove
"clear %l" "\C-d" "Remove breakpoint at current line")
249 (gud-def gud-step
"step %p" "\C-s" "Step one source line with display.")
250 (gud-def gud-stepi
"stepi %p" "\C-i" "Step one instruction with display.")
251 (gud-def gud-next
"next %p" "\C-n" "Step one line (skip functions).")
252 (gud-def gud-cont
"cont" "\C-r" "Continue with display.")
253 (gud-def gud-finish
"finish" "\C-f" "Finish executing current function.")
254 (gud-def gud-up
"up %p" "<" "Up N stack frames (numeric arg).")
255 (gud-def gud-down
"down %p" ">" "Down N stack frames (numeric arg).")
256 (gud-def gud-print
"print %e" "\C-p" "Evaluate C expression at point.")
258 (local-set-key "\C-i" 'gud-gdb-complete-command
)
259 (setq comint-prompt-regexp
"^(.*gdb[+]?) *")
260 (setq paragraph-start comint-prompt-regexp
)
261 (run-hooks 'gdb-mode-hook
)
264 ;; One of the nice features of GDB is its impressive support for
265 ;; context-sensitive command completion. We preserve that feature
266 ;; in the GUD buffer by using a GDB command designed just for Emacs.
268 ;; The completion process filter indicates when it is finished.
269 (defvar gud-gdb-complete-in-progress
)
271 ;; Since output may arrive in fragments we accumulate partials strings here.
272 (defvar gud-gdb-complete-string
)
274 ;; We need to know how much of the completion to chop off.
275 (defvar gud-gdb-complete-break
)
277 ;; The completion list is constructed by the process filter.
278 (defvar gud-gdb-complete-list
)
280 (defvar gud-comint-buffer nil
)
282 (defun gud-gdb-complete-command ()
283 "Perform completion on the GDB command preceding point.
284 This is implemented using the GDB `complete' command which isn't
285 available with older versions of GDB."
288 (command (save-excursion
290 (and (looking-at comint-prompt-regexp
)
291 (goto-char (match-end 0)))
292 (buffer-substring (point) end
)))
294 ;; Find the word break. This match will always succeed.
295 (string-match "\\(\\`\\| \\)\\([^ ]*\\)\\'" command
)
296 (setq gud-gdb-complete-break
(match-beginning 2)
297 command-word
(substring command gud-gdb-complete-break
))
300 ;; Temporarily install our filter function.
301 (gud-overload-functions
302 '((gud-marker-filter . gud-gdb-complete-filter
)))
303 ;; Issue the command to GDB.
304 (gud-basic-call (concat "complete " command
))
305 (setq gud-gdb-complete-in-progress t
306 gud-gdb-complete-string nil
307 gud-gdb-complete-list nil
)
309 (while gud-gdb-complete-in-progress
310 (accept-process-output (get-buffer-process gud-comint-buffer
))))
311 ;; Restore the old filter function.
312 (gud-overload-functions '((gud-marker-filter . gud-gdb-marker-filter
))))
313 ;; Protect against old versions of GDB.
314 (and gud-gdb-complete-list
315 (string-match "^Undefined command: \"complete\""
316 (car gud-gdb-complete-list
))
317 (error "This version of GDB doesn't support the `complete' command."))
318 ;; Sort the list like readline.
319 (setq gud-gdb-complete-list
320 (sort gud-gdb-complete-list
(function string-lessp
)))
321 ;; Remove duplicates.
322 (let ((first gud-gdb-complete-list
)
323 (second (cdr gud-gdb-complete-list
)))
325 (if (string-equal (car first
) (car second
))
326 (setcdr first
(setq second
(cdr second
)))
328 second
(cdr second
)))))
329 ;; Let comint handle the rest.
330 (comint-dynamic-simple-complete command-word gud-gdb-complete-list
)))
332 ;; The completion process filter is installed temporarily to slurp the
333 ;; output of GDB up to the next prompt and build the completion list.
334 (defun gud-gdb-complete-filter (string)
335 (setq string
(concat gud-gdb-complete-string string
))
336 (while (string-match "\n" string
)
337 (setq gud-gdb-complete-list
338 (cons (substring string gud-gdb-complete-break
(match-beginning 0))
339 gud-gdb-complete-list
))
340 (setq string
(substring string
(match-end 0))))
341 (if (string-match comint-prompt-regexp string
)
343 (setq gud-gdb-complete-in-progress nil
)
346 (setq gud-gdb-complete-string string
)
350 ;; ======================================================================
353 ;;; History of argument lists passed to sdb.
354 (defvar gud-sdb-history nil
)
356 (defvar gud-sdb-needs-tags
(not (file-exists-p "/var"))
357 "If nil, we're on a System V Release 4 and don't need the tags hack.")
359 (defvar gud-sdb-lastfile nil
)
361 (defun gud-sdb-massage-args (file args
)
364 (defun gud-sdb-marker-filter (string)
366 ;; System V Release 3.2 uses this format
367 ((string-match "\\(^0x\\w* in \\|^\\|\n\\)\\([^:\n]*\\):\\([0-9]*\\):.*\n"
371 (substring string
(match-beginning 2) (match-end 2))
373 (substring string
(match-beginning 3) (match-end 3))))))
374 ;; System V Release 4.0
375 ((string-match "^\\(BREAKPOINT\\|STEPPED\\) process [0-9]+ function [^ ]+ in \\(.+\\)\n"
377 (setq gud-sdb-lastfile
378 (substring string
(match-beginning 2) (match-end 2))))
379 ((and gud-sdb-lastfile
(string-match "^\\([0-9]+\\):" string
))
384 (substring string
(match-beginning 1) (match-end 1))))))
386 (setq gud-sdb-lastfile nil
)))
389 (defun gud-sdb-find-file (f)
390 (if gud-sdb-needs-tags
391 (find-tag-noselect f
)
392 (find-file-noselect f
)))
395 (defun sdb (command-line)
396 "Run sdb on program FILE in buffer *gud-FILE*.
397 The directory containing FILE becomes the initial working directory
398 and source-file directory for your debugger."
400 (list (read-from-minibuffer "Run sdb (like this): "
401 (if (consp gud-sdb-history
)
402 (car gud-sdb-history
)
405 '(gud-sdb-history .
1))))
406 (if (and gud-sdb-needs-tags
407 (not (and (boundp 'tags-file-name
)
408 (stringp tags-file-name
)
409 (file-exists-p tags-file-name
))))
410 (error "The sdb support requires a valid tags table to work."))
411 (gud-overload-functions '((gud-massage-args . gud-sdb-massage-args
)
412 (gud-marker-filter . gud-sdb-marker-filter
)
413 (gud-find-file . gud-sdb-find-file
)
416 (gud-common-init command-line
)
418 (gud-def gud-break
"%l b" "\C-b" "Set breakpoint at current line.")
419 (gud-def gud-tbreak
"%l c" "\C-t" "Set temporary breakpoint at current line.")
420 (gud-def gud-remove
"%l d" "\C-d" "Remove breakpoint at current line")
421 (gud-def gud-step
"s %p" "\C-s" "Step one source line with display.")
422 (gud-def gud-stepi
"i %p" "\C-i" "Step one instruction with display.")
423 (gud-def gud-next
"S %p" "\C-n" "Step one line (skip functions).")
424 (gud-def gud-cont
"c" "\C-r" "Continue with display.")
425 (gud-def gud-print
"%e/" "\C-p" "Evaluate C expression at point.")
427 (setq comint-prompt-regexp
"\\(^\\|\n\\)\\*")
428 (setq paragraph-start comint-prompt-regexp
)
429 (run-hooks 'sdb-mode-hook
)
432 ;; ======================================================================
435 ;;; History of argument lists passed to dbx.
436 (defvar gud-dbx-history nil
)
438 (defun gud-dbx-massage-args (file args
)
441 (defun gud-dbx-marker-filter (string)
442 (if (or (string-match
443 "stopped in .* at line \\([0-9]*\\) in file \"\\([^\"]*\\)\""
446 "signal .* in .* at line \\([0-9]*\\) in file \"\\([^\"]*\\)\""
450 (substring string
(match-beginning 2) (match-end 2))
452 (substring string
(match-beginning 1) (match-end 1))))))
455 ;; Functions for Mips-style dbx. Given the option `-emacs', documented in
456 ;; OSF1, not necessarily elsewhere, it produces markers similar to gdb's.
458 (or (string-match "^mips-[^-]*-ultrix" system-configuration
)
459 ;; We haven't tested gud on this system:
460 (string-match "^mips-[^-]*-riscos" system-configuration
)
461 ;; It's documented on OSF/1.3
462 (string-match "^mips-[^-]*-osf1" system-configuration
))
463 "Non-nil to assume the MIPS/OSF dbx conventions (argument `-emacs').")
465 (defun gud-mipsdbx-massage-args (file args
)
466 (cons "-emacs" (cons file args
)))
468 ;; This is just like the gdb one except for the regexps since we need to cope
469 ;; with an optional breakpoint number in [] before the ^Z^Z
470 (defun gud-mipsdbx-marker-filter (string)
472 (setq gud-marker-acc
(concat gud-marker-acc string
))
475 ;; Process all the complete markers in this chunk.
477 ;; This is like th gdb marker but with an optional
478 ;; leading break point number like `[1] '
479 "[][ 0-9]*\032\032\\([^:\n]*\\):\\([0-9]*\\):.*\n"
483 ;; Extract the frame position from the marker.
485 (cons (substring gud-marker-acc
(match-beginning 1) (match-end 1))
486 (string-to-int (substring gud-marker-acc
490 ;; Append any text before the marker to the output we're going
491 ;; to return - we don't include the marker in this text.
492 output
(concat output
493 (substring gud-marker-acc
0 (match-beginning 0)))
495 ;; Set the accumulator to the remaining text.
496 gud-marker-acc
(substring gud-marker-acc
(match-end 0))))
498 ;; Does the remaining text look like it might end with the
499 ;; beginning of another marker? If it does, then keep it in
500 ;; gud-marker-acc until we receive the rest of it. Since we
501 ;; know the full marker regexp above failed, it's pretty simple to
502 ;; test for marker starts.
503 (if (string-match "[][ 0-9]*\032.*\\'" gud-marker-acc
)
505 ;; Everything before the potential marker start can be output.
506 (setq output
(concat output
(substring gud-marker-acc
507 0 (match-beginning 0))))
509 ;; Everything after, we save, to combine with later input.
511 (substring gud-marker-acc
(match-beginning 0))))
513 (setq output
(concat output gud-marker-acc
)
518 ;; The dbx in IRIX is a pain. It doesn't print the file name when
519 ;; stopping at a breakpoint (but you do get it from the `up' and
520 ;; `down' commands...). The only way to extract the information seems
521 ;; to be with a `file' command, although the current line number is
522 ;; available in $curline. Thus we have to look for output which
523 ;; appears to indicate a breakpoint. Then we prod the dbx sub-process
524 ;; to output the information we want with a combination of the
525 ;; `printf' and `file' commands as a pseudo marker which we can
526 ;; recognise next time through the marker-filter. This would be like
527 ;; the gdb marker but you can't get the file name without a newline...
528 ;; Note that gud-remove won't work since Irix dbx expects a breakpoint
529 ;; number rather than a line number etc. Maybe this could be made to
530 ;; work by listing all the breakpoints and picking the one(s) with the
531 ;; correct line number, but life's too short.
532 ;; d.love@dl.ac.uk (Dave Love) can be blamed for this
534 (defvar gud-irix-p
(string-match "^mips-[^-]*-irix" system-configuration
)
535 "Non-nil to assume the interface appropriate for IRIX dbx.
536 This works in IRIX 4 and probably IRIX 5.")
537 ;; (It's been tested in IRIX 4 and the output from dbx on IRIX 5 looks
540 ;; this filter is influenced by the xdb one rather than the gdb one
541 (defun gud-irixdbx-marker-filter (string)
543 (let (result (case-fold-search nil
))
544 (if (or (string-match comint-prompt-regexp string
)
545 (string-match ".*\012" string
))
546 (setq result
(concat gud-marker-acc string
)
548 (setq gud-marker-acc
(concat gud-marker-acc string
)))
551 ;; look for breakpoint or signal indication e.g.:
552 ;; [2] Process 1267 (pplot) stopped at [params:338 ,0x400ec0]
553 ;; Process 1281 (pplot) stopped at [params:339 ,0x400ec8]
554 ;; Process 1270 (pplot) Floating point exception [._read._read:16 ,0x452188]
556 "^\\(\\[[0-9]+] \\)?Process +[0-9]+ ([^)]*) [^[]+\\[[^]\n]*]\n"
558 ;; prod dbx into printing out the line number and file
559 ;; name in a form we can grok as below
560 (process-send-string (get-buffer-process gud-comint-buffer
)
561 "printf \"\032\032%1d:\",$curline;file\n"))
562 ;; look for result of, say, "up" e.g.:
563 ;; .pplot.pplot(0x800) ["src/pplot.f":261, 0x400c7c]
564 ;; (this will also catch one of the lines printed by "where")
566 "^[^ ][^[]*\\[\"\\([^\"]+\\)\":\\([0-9]+\\), [^]]+]\n"
568 (let ((file (substring result
(match-beginning 1)
570 (if (file-exists-p file
)
574 result
(match-beginning 1) (match-end 1))
577 result
(match-beginning 2) (match-end 2)))))))
579 ((string-match ; kluged-up marker as above
580 "\032\032\\([0-9]*\\):\\(.*\\)\n" result
)
581 (let ((file (substring result
(match-beginning 2) (match-end 2))))
582 (if (file-exists-p file
)
588 result
(match-beginning 1) (match-end 1)))))))
589 (setq result
(substring result
0 (match-beginning 0))))))
592 (defun gud-dbx-find-file (f)
593 (find-file-noselect f
))
596 (defun dbx (command-line)
597 "Run dbx on program FILE in buffer *gud-FILE*.
598 The directory containing FILE becomes the initial working directory
599 and source-file directory for your debugger."
601 (list (read-from-minibuffer "Run dbx (like this): "
602 (if (consp gud-dbx-history
)
603 (car gud-dbx-history
)
606 '(gud-dbx-history .
1))))
608 (gud-overload-functions
611 '((gud-massage-args . gud-mipsdbx-massage-args
)
612 (gud-marker-filter . gud-mipsdbx-marker-filter
)
613 (gud-find-file . gud-dbx-find-file
)))
615 '((gud-massage-args . gud-dbx-massage-args
)
616 (gud-marker-filter . gud-irixdbx-marker-filter
)
617 (gud-find-file . gud-dbx-find-file
)))
619 '((gud-massage-args . gud-dbx-massage-args
)
620 (gud-marker-filter . gud-dbx-marker-filter
)
621 (gud-find-file . gud-dbx-find-file
)))))
623 (gud-common-init command-line
)
627 (gud-def gud-break
"stop at \"%f\":%l"
628 "\C-b" "Set breakpoint at current line.")
629 (gud-def gud-finish
"return" "\C-f" "Finish executing current function."))
631 (gud-def gud-break
"stop at \"%d%f\":%l"
632 "\C-b" "Set breakpoint at current line.")
633 (gud-def gud-finish
"return" "\C-f" "Finish executing current function.")
634 ;; Make dbx give out the source location info that we need.
635 (process-send-string (get-buffer-process gud-comint-buffer
)
636 "printf \"\032\032%1d:\",$curline;file\n"))
637 ((or (string-match "-sunos" (symbol-name system-type
))
638 (string-match "-solaris" (symbol-name system-type
)))
639 ;; The following works for both the UCB and SunPro 2.0.1 versions
640 ;; of dbx. The `stop' is lost using the `\n' separator as in the
641 ;; default case. Is there a dbx where the newline is actually
642 ;; necessary? (d.love@dl.ac.uk)
643 (gud-def gud-break
"file \"%d%f\";stop at %l"
644 "\C-b" "Set breakpoint at current line."))
646 (gud-def gud-break
"file \"%d%f\"\nstop at %l"
647 "\C-b" "Set breakpoint at current line.")))
649 (gud-def gud-remove
"clear %l" "\C-d" "Remove breakpoint at current line")
650 (gud-def gud-step
"step %p" "\C-s" "Step one line with display.")
651 (gud-def gud-stepi
"stepi %p" "\C-i" "Step one instruction with display.")
652 (gud-def gud-next
"next %p" "\C-n" "Step one line (skip functions).")
653 (gud-def gud-cont
"cont" "\C-r" "Continue with display.")
654 (gud-def gud-up
"up %p" "<" "Up (numeric arg) stack frames.")
655 (gud-def gud-down
"down %p" ">" "Down (numeric arg) stack frames.")
656 (gud-def gud-print
"print %e" "\C-p" "Evaluate C expression at point.")
658 (setq comint-prompt-regexp
"^[^)\n]*dbx) *")
659 (setq paragraph-start comint-prompt-regexp
)
660 (run-hooks 'dbx-mode-hook
)
663 ;; ======================================================================
664 ;; xdb (HP PARISC debugger) functions
666 ;;; History of argument lists passed to xdb.
667 (defvar gud-xdb-history nil
)
669 (defvar gud-xdb-directories nil
670 "*A list of directories that xdb should search for source code.
671 If nil, only source files in the program directory
672 will be known to xdb.
674 The file names should be absolute, or relative to the directory
675 containing the executable being debugged.")
677 (defun gud-xdb-massage-args (file args
)
678 (nconc (let ((directories gud-xdb-directories
)
681 (setq result
(cons (car directories
) (cons "-d" result
)))
682 (setq directories
(cdr directories
)))
683 (nreverse (cons file result
)))
686 (defun gud-xdb-file-name (f)
687 "Transform a relative pathname to a full pathname in xdb mode"
689 (if (file-exists-p f
)
690 (setq result
(expand-file-name f
))
691 (let ((directories gud-xdb-directories
))
693 (let ((path (concat (car directories
) "/" f
)))
694 (if (file-exists-p path
)
695 (setq result
(expand-file-name path
)
697 (setq directories
(cdr directories
)))))
700 ;; xdb does not print the lines all at once, so we have to accumulate them
701 (defun gud-xdb-marker-filter (string)
703 (if (or (string-match comint-prompt-regexp string
)
704 (string-match ".*\012" string
))
705 (setq result
(concat gud-marker-acc string
)
707 (setq gud-marker-acc
(concat gud-marker-acc string
)))
709 (if (or (string-match "\\([^\n \t:]+\\): [^:]+: \\([0-9]+\\):" result
)
710 (string-match "[^: \t]+:[ \t]+\\([^:]+\\): [^:]+: \\([0-9]+\\):"
712 (let ((line (string-to-int
713 (substring result
(match-beginning 2) (match-end 2))))
714 (file (gud-xdb-file-name
715 (substring result
(match-beginning 1) (match-end 1)))))
717 (setq gud-last-frame
(cons file line
))))))
720 (defun gud-xdb-find-file (f)
721 (let ((realf (gud-xdb-file-name f
)))
722 (if realf
(find-file-noselect realf
))))
725 (defun xdb (command-line)
726 "Run xdb on program FILE in buffer *gud-FILE*.
727 The directory containing FILE becomes the initial working directory
728 and source-file directory for your debugger.
730 You can set the variable 'gud-xdb-directories' to a list of program source
731 directories if your program contains sources from more than one directory."
733 (list (read-from-minibuffer "Run xdb (like this): "
734 (if (consp gud-xdb-history
)
735 (car gud-xdb-history
)
738 '(gud-xdb-history .
1))))
739 (gud-overload-functions '((gud-massage-args . gud-xdb-massage-args
)
740 (gud-marker-filter . gud-xdb-marker-filter
)
741 (gud-find-file . gud-xdb-find-file
)))
743 (gud-common-init command-line
)
745 (gud-def gud-break
"b %f:%l" "\C-b" "Set breakpoint at current line.")
746 (gud-def gud-tbreak
"b %f:%l\\t" "\C-t"
747 "Set temporary breakpoint at current line.")
748 (gud-def gud-remove
"db" "\C-d" "Remove breakpoint at current line")
749 (gud-def gud-step
"s %p" "\C-s" "Step one line with display.")
750 (gud-def gud-next
"S %p" "\C-n" "Step one line (skip functions).")
751 (gud-def gud-cont
"c" "\C-r" "Continue with display.")
752 (gud-def gud-up
"up %p" "<" "Up (numeric arg) stack frames.")
753 (gud-def gud-down
"down %p" ">" "Down (numeric arg) stack frames.")
754 (gud-def gud-finish
"bu\\t" "\C-f" "Finish executing current function.")
755 (gud-def gud-print
"p %e" "\C-p" "Evaluate C expression at point.")
757 (setq comint-prompt-regexp
"^>")
758 (setq paragraph-start comint-prompt-regexp
)
759 (run-hooks 'xdb-mode-hook
))
761 ;; ======================================================================
764 ;;; History of argument lists passed to perldb.
765 (defvar gud-perldb-history nil
)
767 (defun gud-perldb-massage-args (file args
)
768 (cons "-d" (cons file
(cons "-emacs" args
))))
770 ;; There's no guarantee that Emacs will hand the filter the entire
771 ;; marker at once; it could be broken up across several strings. We
772 ;; might even receive a big chunk with several markers in it. If we
773 ;; receive a chunk of text which looks like it might contain the
774 ;; beginning of a marker, we save it here between calls to the
776 (defvar gud-perldb-marker-acc
"")
778 (defun gud-perldb-marker-filter (string)
780 (setq gud-marker-acc
(concat gud-marker-acc string
))
783 ;; Process all the complete markers in this chunk.
784 (while (string-match "\032\032\\([^:\n]*\\):\\([0-9]*\\):.*\n"
788 ;; Extract the frame position from the marker.
790 (cons (substring gud-marker-acc
(match-beginning 1) (match-end 1))
791 (string-to-int (substring gud-marker-acc
795 ;; Append any text before the marker to the output we're going
796 ;; to return - we don't include the marker in this text.
797 output
(concat output
798 (substring gud-marker-acc
0 (match-beginning 0)))
800 ;; Set the accumulator to the remaining text.
801 gud-marker-acc
(substring gud-marker-acc
(match-end 0))))
803 ;; Does the remaining text look like it might end with the
804 ;; beginning of another marker? If it does, then keep it in
805 ;; gud-marker-acc until we receive the rest of it. Since we
806 ;; know the full marker regexp above failed, it's pretty simple to
807 ;; test for marker starts.
808 (if (string-match "\032.*\\'" gud-marker-acc
)
810 ;; Everything before the potential marker start can be output.
811 (setq output
(concat output
(substring gud-marker-acc
812 0 (match-beginning 0))))
814 ;; Everything after, we save, to combine with later input.
816 (substring gud-marker-acc
(match-beginning 0))))
818 (setq output
(concat output gud-marker-acc
)
823 (defun gud-perldb-find-file (f)
824 (find-file-noselect f
))
827 (defun perldb (command-line)
828 "Run perldb on program FILE in buffer *gud-FILE*.
829 The directory containing FILE becomes the initial working directory
830 and source-file directory for your debugger."
832 (list (read-from-minibuffer "Run perldb (like this): "
833 (if (consp gud-perldb-history
)
834 (car gud-perldb-history
)
837 '(gud-perldb-history .
1))))
838 (gud-overload-functions '((gud-massage-args . gud-perldb-massage-args
)
839 (gud-marker-filter . gud-perldb-marker-filter
)
840 (gud-find-file . gud-perldb-find-file
)
843 (gud-common-init command-line
)
845 (gud-def gud-break
"b %l" "\C-b" "Set breakpoint at current line.")
846 (gud-def gud-remove
"d %l" "\C-d" "Remove breakpoint at current line")
847 (gud-def gud-step
"s" "\C-s" "Step one source line with display.")
848 (gud-def gud-next
"n" "\C-n" "Step one line (skip functions).")
849 (gud-def gud-cont
"c" "\C-r" "Continue with display.")
850 ; (gud-def gud-finish "finish" "\C-f" "Finish executing current function.")
851 ; (gud-def gud-up "up %p" "<" "Up N stack frames (numeric arg).")
852 ; (gud-def gud-down "down %p" ">" "Down N stack frames (numeric arg).")
853 (gud-def gud-print
"%e" "\C-p" "Evaluate perl expression at point.")
855 (setq comint-prompt-regexp
"^ DB<[0-9]+> ")
856 (setq paragraph-start comint-prompt-regexp
)
857 (run-hooks 'perldb-mode-hook
)
861 ;; End of debugger-specific information
865 ;;; When we send a command to the debugger via gud-call, it's annoying
866 ;;; to see the command and the new prompt inserted into the debugger's
867 ;;; buffer; we have other ways of knowing the command has completed.
869 ;;; If the buffer looks like this:
870 ;;; --------------------
871 ;;; (gdb) set args foo bar
873 ;;; --------------------
874 ;;; (the -!- marks the location of point), and we type `C-x SPC' in a
875 ;;; source file to set a breakpoint, we want the buffer to end up like
877 ;;; --------------------
878 ;;; (gdb) set args foo bar
879 ;;; Breakpoint 1 at 0x92: file make-docfile.c, line 49.
881 ;;; --------------------
882 ;;; Essentially, the old prompt is deleted, and the command's output
883 ;;; and the new prompt take its place.
885 ;;; Not echoing the command is easy enough; you send it directly using
886 ;;; process-send-string, and it never enters the buffer. However,
887 ;;; getting rid of the old prompt is trickier; you don't want to do it
888 ;;; when you send the command, since that will result in an annoying
889 ;;; flicker as the prompt is deleted, redisplay occurs while Emacs
890 ;;; waits for a response from the debugger, and the new prompt is
891 ;;; inserted. Instead, we'll wait until we actually get some output
892 ;;; from the subprocess before we delete the prompt. If the command
893 ;;; produced no output other than a new prompt, that prompt will most
894 ;;; likely be in the first chunk of output received, so we will delete
895 ;;; the prompt and then replace it with an identical one. If the
896 ;;; command produces output, the prompt is moving anyway, so the
897 ;;; flicker won't be annoying.
899 ;;; So - when we want to delete the prompt upon receipt of the next
900 ;;; chunk of debugger output, we position gud-delete-prompt-marker at
901 ;;; the start of the prompt; the process filter will notice this, and
902 ;;; delete all text between it and the process output marker. If
903 ;;; gud-delete-prompt-marker points nowhere, we leave the current
905 (defvar gud-delete-prompt-marker nil
)
909 "Major mode for interacting with an inferior debugger process.
911 You start it up with one of the commands M-x gdb, M-x sdb, M-x dbx,
912 or M-x xdb. Each entry point finishes by executing a hook; `gdb-mode-hook',
913 `sdb-mode-hook', `dbx-mode-hook' or `xdb-mode-hook' respectively.
915 After startup, the following commands are available in both the GUD
916 interaction buffer and any source buffer GUD visits due to a breakpoint stop
919 \\[gud-break] sets a breakpoint at the current file and line. In the
920 GUD buffer, the current file and line are those of the last breakpoint or
921 step. In a source buffer, they are the buffer's file and current line.
923 \\[gud-remove] removes breakpoints on the current file and line.
925 \\[gud-refresh] displays in the source window the last line referred to
928 \\[gud-step], \\[gud-next], and \\[gud-stepi] do a step-one-line,
929 step-one-line (not entering function calls), and step-one-instruction
930 and then update the source window with the current file and position.
931 \\[gud-cont] continues execution.
933 \\[gud-print] tries to find the largest C lvalue or function-call expression
934 around point, and sends it to the debugger for value display.
936 The above commands are common to all supported debuggers except xdb which
937 does not support stepping instructions.
939 Under gdb, sdb and xdb, \\[gud-tbreak] behaves exactly like \\[gud-break],
940 except that the breakpoint is temporary; that is, it is removed when
941 execution stops on it.
943 Under gdb, dbx, and xdb, \\[gud-up] pops up through an enclosing stack
944 frame. \\[gud-down] drops back down through one.
946 If you are using gdb or xdb, \\[gud-finish] runs execution to the return from
947 the current function and stops.
949 All the keystrokes above are accessible in the GUD buffer
950 with the prefix C-c, and in all buffers through the prefix C-x C-a.
952 All pre-defined functions for which the concept make sense repeat
953 themselves the appropriate number of times if you give a prefix
956 You may use the `gud-def' macro in the initialization hook to define other
959 Other commands for interacting with the debugger process are inherited from
960 comint mode, which see."
963 (setq major-mode
'gud-mode
)
964 (setq mode-name
"Debugger")
965 (setq mode-line-process
'(":%s"))
966 (use-local-map (copy-keymap comint-mode-map
))
967 (define-key (current-local-map) "\C-c\C-l" 'gud-refresh
)
968 (make-local-variable 'gud-last-frame
)
969 (setq gud-last-frame nil
)
970 (make-local-variable 'comint-prompt-regexp
)
971 (make-local-variable 'paragraph-start
)
972 (make-local-variable 'gud-delete-prompt-marker
)
973 (setq gud-delete-prompt-marker
(make-marker))
974 (run-hooks 'gud-mode-hook
)
977 ;; Chop STRING into words separated by SPC or TAB and return a list of them.
978 (defun gud-chop-words (string)
980 (len (length string
))
983 (if (memq (aref string i
) '(?
\t ?
))
985 (setq words
(cons (substring string beg i
) words
)
987 (while (and (< beg len
) (memq (aref string beg
) '(?
\t ?
)))
992 (setq words
(cons (substring string beg
) words
)))
995 ;; Perform initializations common to all debuggers.
996 (defun gud-common-init (command-line)
997 (let* ((words (gud-chop-words command-line
))
998 (program (car words
))
999 (file-word (let ((w (cdr words
)))
1000 (while (and w
(= ?-
(aref (car w
) 0)))
1003 (args (delq file-word
(cdr words
)))
1004 (file (and file-word
1005 (expand-file-name (substitute-in-file-name file-word
))))
1006 (filepart (and file-word
(file-name-nondirectory file
))))
1007 (switch-to-buffer (concat "*gud-" filepart
"*"))
1008 (and file-word
(setq default-directory
(file-name-directory file
)))
1009 (or (bolp) (newline))
1010 (insert "Current directory is " default-directory
"\n")
1011 (apply 'make-comint
(concat "gud-" filepart
) program nil
1012 (if file-word
(gud-massage-args file args
))))
1014 (set-process-filter (get-buffer-process (current-buffer)) 'gud-filter
)
1015 (set-process-sentinel (get-buffer-process (current-buffer)) 'gud-sentinel
)
1019 (defun gud-set-buffer ()
1020 (cond ((eq major-mode
'gud-mode
)
1021 (setq gud-comint-buffer
(current-buffer)))))
1023 ;; These functions are responsible for inserting output from your debugger
1024 ;; into the buffer. The hard work is done by the method that is
1025 ;; the value of gud-marker-filter.
1027 (defun gud-filter (proc string
)
1028 ;; Here's where the actual buffer insertion is done
1029 (let ((inhibit-quit t
)
1032 (set-buffer (process-buffer proc
))
1033 ;; If we have been so requested, delete the debugger prompt.
1034 (if (marker-buffer gud-delete-prompt-marker
)
1036 (delete-region (process-mark proc
) gud-delete-prompt-marker
)
1037 (set-marker gud-delete-prompt-marker nil
)))
1038 ;; Save the process output, checking for source file markers.
1039 (setq output
(gud-marker-filter string
))
1040 ;; Check for a filename-and-line number.
1041 ;; Don't display the specified file
1042 ;; unless (1) point is at or after the position where output appears
1043 ;; and (2) this buffer is on the screen.
1044 (if (and gud-last-frame
1045 (>= (point) (process-mark proc
))
1046 (get-buffer-window (current-buffer)))
1047 (gud-display-frame))
1048 ;; Let the comint filter do the actual insertion.
1049 ;; That lets us inherit various comint features.
1050 (comint-output-filter proc output
))))
1052 (defun gud-sentinel (proc msg
)
1053 (cond ((null (buffer-name (process-buffer proc
)))
1055 ;; Stop displaying an arrow in a source file.
1056 (setq overlay-arrow-position nil
)
1057 (set-process-buffer proc nil
))
1058 ((memq (process-status proc
) '(signal exit
))
1059 ;; Stop displaying an arrow in a source file.
1060 (setq overlay-arrow-position nil
)
1061 ;; Fix the mode line.
1062 (setq mode-line-process
1064 (symbol-name (process-status proc
))))
1065 (let* ((obuf (current-buffer)))
1066 ;; save-excursion isn't the right thing if
1067 ;; process-buffer is current-buffer
1070 ;; Write something in *compilation* and hack its mode line,
1071 (set-buffer (process-buffer proc
))
1072 ;; Force mode line redisplay soon
1073 (set-buffer-modified-p (buffer-modified-p))
1075 (insert ?
\n mode-name
" " msg
)
1077 (goto-char (point-max))
1078 (insert ?
\n mode-name
" " msg
)))
1079 ;; If buffer and mode line will show that the process
1080 ;; is dead, we can delete it now. Otherwise it
1081 ;; will stay around until M-x list-processes.
1082 (delete-process proc
))
1083 ;; Restore old buffer, but don't restore old point
1084 ;; if obuf is the gud buffer.
1085 (set-buffer obuf
))))))
1087 (defun gud-display-frame ()
1088 "Find and obey the last filename-and-line marker from the debugger.
1089 Obeying it means displaying in another window the specified file and line."
1094 (gud-display-line (car gud-last-frame
) (cdr gud-last-frame
))
1095 (setq gud-last-last-frame gud-last-frame
1096 gud-last-frame nil
))))
1098 ;; Make sure the file named TRUE-FILE is in a buffer that appears on the screen
1099 ;; and that its line LINE is visible.
1100 ;; Put the overlay-arrow on the line LINE in that buffer.
1101 ;; Most of the trickiness in here comes from wanting to preserve the current
1102 ;; region-restriction if that's possible. We use an explicit display-buffer
1103 ;; to get around the fact that this is called inside a save-excursion.
1105 (defun gud-display-line (true-file line
)
1106 (let* ((last-nonmenu-event t
) ; Prevent use of dialog box for questions.
1107 (buffer (gud-find-file true-file
))
1108 (window (display-buffer buffer
))
1110 ;;; (if (equal buffer (current-buffer))
1112 ;;; (setq buffer-read-only nil))
1114 ;;; (setq buffer-read-only t)
1120 (setq overlay-arrow-string
"=>")
1121 (or overlay-arrow-position
1122 (setq overlay-arrow-position
(make-marker)))
1123 (set-marker overlay-arrow-position
(point) (current-buffer)))
1124 (cond ((or (< pos
(point-min)) (> pos
(point-max)))
1127 (set-window-point window overlay-arrow-position
)))
1129 ;;; The gud-call function must do the right thing whether its invoking
1130 ;;; keystroke is from the GUD buffer itself (via major-mode binding)
1131 ;;; or a C buffer. In the former case, we want to supply data from
1132 ;;; gud-last-frame. Here's how we do it:
1134 (defun gud-format-command (str arg
)
1135 (let ((insource (not (eq (current-buffer) gud-comint-buffer
)))
1136 (frame (or gud-last-frame gud-last-last-frame
))
1138 (while (and str
(string-match "\\([^%]*\\)%\\([adeflp]\\)" str
))
1139 (let ((key (string-to-char (substring str
(match-beginning 2))))
1143 (setq subst
(file-name-nondirectory (if insource
1147 (setq subst
(file-name-directory (if insource
1151 (setq subst
(if insource
1154 (save-restriction (widen)
1155 (1+ (count-lines 1 (point)))))
1158 (setq subst
(find-c-expr)))
1160 (setq subst
(gud-read-address)))
1162 (setq subst
(if arg
(int-to-string arg
) ""))))
1163 (setq result
(concat result
1164 (substring str
(match-beginning 1) (match-end 1))
1166 (setq str
(substring str
(match-end 2))))
1167 ;; There might be text left in STR when the loop ends.
1168 (concat result str
)))
1170 (defun gud-read-address ()
1171 "Return a string containing the core-address found in the buffer at point."
1173 (let ((pt (point)) found begin
)
1174 (setq found
(if (search-backward "0x" (- pt
7) t
) (point)))
1176 (found (forward-char 2)
1177 (buffer-substring found
1178 (progn (re-search-forward "[^0-9a-f]")
1181 (t (setq begin
(progn (re-search-backward "[^0-9]")
1185 (re-search-forward "[^0-9]")
1187 (buffer-substring begin
(point)))))))
1189 (defun gud-call (fmt &optional arg
)
1190 (let ((msg (gud-format-command fmt arg
)))
1191 (message "Command: %s" msg
)
1193 (gud-basic-call msg
)))
1195 (defun gud-basic-call (command)
1196 "Invoke the debugger COMMAND displaying source in other window."
1199 (let ((command (concat command
"\n"))
1200 (proc (get-buffer-process gud-comint-buffer
)))
1202 ;; Arrange for the current prompt to get deleted.
1204 (set-buffer gud-comint-buffer
)
1205 (goto-char (process-mark proc
))
1207 (if (looking-at comint-prompt-regexp
)
1208 (set-marker gud-delete-prompt-marker
(point))))
1209 (process-send-string proc command
)))
1211 (defun gud-refresh (&optional arg
)
1212 "Fix up a possibly garbled display, and redraw the arrow."
1215 (or gud-last-frame
(setq gud-last-frame gud-last-last-frame
))
1216 (gud-display-frame))
1218 ;;; Code for parsing expressions out of C code. The single entry point is
1219 ;;; find-c-expr, which tries to return an lvalue expression from around point.
1221 ;;; The rest of this file is a hacked version of gdbsrc.el by
1222 ;;; Debby Ayers <ayers@asc.slb.com>,
1223 ;;; Rich Schaefer <schaefer@asc.slb.com> Schlumberger, Austin, Tx.
1225 (defun find-c-expr ()
1226 "Returns the C expr that surrounds point."
1229 (let ((p) (expr) (test-expr))
1231 (setq expr
(expr-cur))
1232 (setq test-expr
(expr-prev))
1233 (while (expr-compound test-expr expr
)
1234 (setq expr
(cons (car test-expr
) (cdr expr
)))
1235 (goto-char (car expr
))
1236 (setq test-expr
(expr-prev)))
1238 (setq test-expr
(expr-next))
1239 (while (expr-compound expr test-expr
)
1240 (setq expr
(cons (car expr
) (cdr test-expr
)))
1241 (setq test-expr
(expr-next))
1243 (buffer-substring (car expr
) (cdr expr
)))))
1246 "Returns the expr that point is in; point is set to beginning of expr.
1247 The expr is represented as a cons cell, where the car specifies the point in
1248 the current buffer that marks the beginning of the expr and the cdr specifies
1249 the character after the end of the expr."
1250 (let ((p (point)) (begin) (end))
1251 (expr-backward-sexp)
1252 (setq begin
(point))
1266 (defun expr-backward-sexp ()
1267 "Version of `backward-sexp' that catches errors."
1272 (defun expr-forward-sexp ()
1273 "Version of `forward-sexp' that catches errors."
1279 "Returns the previous expr, point is set to beginning of that expr.
1280 The expr is represented as a cons cell, where the car specifies the point in
1281 the current buffer that marks the beginning of the expr and the cdr specifies
1282 the character after the end of the expr"
1283 (let ((begin) (end))
1284 (expr-backward-sexp)
1285 (setq begin
(point))
1292 "Returns the following expr, point is set to beginning of that expr.
1293 The expr is represented as a cons cell, where the car specifies the point in
1294 the current buffer that marks the beginning of the expr and the cdr specifies
1295 the character after the end of the expr."
1296 (let ((begin) (end))
1300 (expr-backward-sexp)
1301 (setq begin
(point))
1304 (defun expr-compound-sep (span-start span-end
)
1305 "Returns '.' for '->' & '.', returns ' ' for white space,
1306 returns '?' for other punctuation."
1309 (while (< span-start span-end
)
1310 (setq syntax
(char-syntax (char-after span-start
)))
1313 ((= syntax ?.
) (setq syntax
(char-after span-start
))
1315 ((= syntax ?.
) (setq result ?.
))
1316 ((and (= syntax ?-
) (= (char-after (+ span-start
1)) ?
>))
1318 (setq span-start
(+ span-start
1)))
1319 (t (setq span-start span-end
)
1320 (setq result ??
)))))
1321 (setq span-start
(+ span-start
1)))
1324 (defun expr-compound (first second
)
1325 "Non-nil if concatenating FIRST and SECOND makes a single C token.
1326 The two exprs are represented as a cons cells, where the car
1327 specifies the point in the current buffer that marks the beginning of the
1328 expr and the cdr specifies the character after the end of the expr.
1329 Link exprs of the form:
1336 (let ((span-start (cdr first
))
1337 (span-end (car second
))
1339 (setq syntax
(expr-compound-sep span-start span-end
))
1341 ((= (car first
) (car second
)) nil
)
1342 ((= (cdr first
) (cdr second
)) nil
)
1345 (setq span-start
(char-after (- span-start
1)))
1346 (setq span-end
(char-after span-end
))
1348 ((= span-start ?
) ) t
)
1349 ((= span-start ?
] ) t
)
1350 ((= span-end ?
( ) t
)
1351 ((= span-end ?
[ ) t
)
1358 ;;; gud.el ends here