Re: gud/gdb

[Nick Roberts]

 > The problem is hard to explain how to reproduce, but occasionally gdb gets
 > really confused and, in addition to not displaying the buffer with the
 > source code where the program has stopped, it also issues numerous error
 > messages from the process filter.

Does it happen if you enter commands more slowly, e.g. when stepping, in the
GUD buffer so that the program being debugged has time to stop before the next
command?  Also if you step using the toolbar you shouldn't see this problem
(commands issued while the program is running get disregarded).

 > Here is the fix I found that worked for me.  Someone who understands gud
 > better than I should check the fix for correctness.

Before applying such a patch we would need a test to reproduce the problem and
a rationale for the fix but I doubt that this is indeed a fix and suspect that
simply the timing of the commands you entered differed.  I am aware of such
problems but can't see a simple solution.

 >      lisp/progmodes/gud.el
 > 
 > change
 > 
 > (defvar gud-gdb-marker-regexp
 >   ;; This used to use path-separator instead of ":";
 >   ;; however, we found that on both Windows 32 and MSDOS
 >   ;; a colon is correct here.
 >   (concat "\032\032\\(.:?[^" ":" "\n]*\\)" ":"
 >        "\\([0-9]*\\)" ":" ".*\n"))
 > 
 > to
 > 
 > (defvar gud-gdb-marker-regexp
 >   ;; This used to use path-separator instead of ":";
 >   ;; however, we found that on both Windows 32 and MSDOS
 >   ;; a colon is correct here.
 >   (concat "\032\032source \\(.:?[^" ":" "\n]*\\)" ":"
 >        "\\([0-9]*\\)" ":" ".*\n"))




-- 
Nick                                           http://www.inet.net.nz/~nickrob