[Python-bugs-list] [ python-Bugs-606250 ] python-mode kills arrow in gdb (gud.el)

noreply@sourceforge.net noreply@sourceforge.net
Fri, 01 Nov 2002 18:51:59 -0800


Bugs item #606250, was opened at 2002-09-08 04:21
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=606250&group_id=5470

>Category: Demos and Tools
Group: Python 2.3
Status: Open
Resolution: None
Priority: 5
Submitted By: Matthias Klose (doko)
>Assigned to: Barry A. Warsaw (bwarsaw)
Summary: python-mode kills arrow in gdb (gud.el)

Initial Comment:
[ forwarded from http://bugs.debian.org/159628 ]

missing proper category ...

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:

 (add-hook 'comint-output-filter-functions
'py-pdbtrack-track-stack-file)

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
global hook?

(took forever to figure out it was python-mode causing
the problem..)


----------------------------------------------------------------------

>Comment By: Neal Norwitz (nnorwitz)
Date: 2002-11-01 21:51

Message:
Logged In: YES 
user_id=33168

Barry, I thought you worked on this?  Perhaps this is a
duplicate?

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=606250&group_id=5470