Once python-mode.el has been loaded, all GDB buffers
stop showing the little arrow that lives in the
"fringe" on the left side of an emacs21 frame. To be
specific, the arrow appears and then disappears right
away, each time a 'step' or 'next' command is run. I
traced the problem down to the unconditional hooking of
'comint-output-filter-functions, python-mode.el line
3472 to be exact:
I haven't tested it fully, but I've found that if I
take this line out, GDB can show its arrow once more.
There is code in python-mode.el to insert this hook in
a buffer-local fashion only in the '*Python*' buffer..
maybe that should be reviewed and used instead of this
(took forever to figure out it was python-mode causing
This one is still broken for me, in python-mode 4.40. (I'm
the submitter of the original debian bug report).
Here are some instructions to reproduce the problem:
574:warner@cinla% cat hello.c
575:warner@cinla% gcc -g -o hello hello.c
577:warner@cinla% cat foo.py
578:warner@cinla% emacs -q
M-x gdb hello RET # starts GUD session
(gdb) b main RET
(gdb) run RET # GDB stops on "hello".
arrow in fringe.
C-x C-f foo.py RET # loads python-mode.el
C-x b *gud-hello* RET # switch back to GDB buffer
(gdb) next RET # GDB stops on "world".
lack of arrow.
(gdb) next RET # arrow flickers and
disappears each time
emacs-version reports "GNU Emacs 21.3.1 (i386-pc-linux-gnu,
X toolkit) of 2003-10-31 on raven, modified by Debian"
this is package emacs21, version 21.3+1-4 (from unstable)
python-elisp is version 220.127.116.11-1, with py-version at
$Revision: 4.40 $
let me know if there is anything I can do to further track