summaryrefslogtreecommitdiff
path: root/lisp/gud.el
diff options
context:
space:
mode:
authorKarl Heuer <kwzh@gnu.org>1995-05-27 00:36:36 +0000
committerKarl Heuer <kwzh@gnu.org>1995-05-27 00:36:36 +0000
commitb118521eed59d6b763665a8016483a5a65c36dc6 (patch)
treea6a89e1190e9cdec9b3ffe1de1705c7610b55794 /lisp/gud.el
parent579b6c9d8c9981db62c2f2926a26e877f57e80fa (diff)
downloademacs-b118521eed59d6b763665a8016483a5a65c36dc6.tar.gz
(gud-gdb-marker-regexp): New var. Use path-separator.
Diffstat (limited to 'lisp/gud.el')
-rw-r--r--lisp/gud.el7
1 files changed, 5 insertions, 2 deletions
diff --git a/lisp/gud.el b/lisp/gud.el
index 75f56b90d45..a12c84c5fda 100644
--- a/lisp/gud.el
+++ b/lisp/gud.el
@@ -170,6 +170,10 @@ we're in the GUD buffer)."
(defun gud-gdb-massage-args (file args)
(cons "-fullname" args))
+(defvar gud-gdb-marker-regexp
+ (concat "\032\032\\([^" path-separator "\n]*\\)" path-separator
+ "\\([0-9]*\\)" path-separator ".*\n"))
+
;; There's no guarantee that Emacs will hand the filter the entire
;; marker at once; it could be broken up across several strings. We
;; might even receive a big chunk with several markers in it. If we
@@ -184,8 +188,7 @@ we're in the GUD buffer)."
(let ((output ""))
;; Process all the complete markers in this chunk.
- (while (string-match "\032\032\\([^:\n]*\\):\\([0-9]*\\):.*\n"
- gud-marker-acc)
+ (while (string-match gud-gdb-marker-regexp gud-marker-acc)
(setq
;; Extract the frame position from the marker.