[Patches] [ python-Patches-567468 ] A different patch for python-mode vs gdb

[noreply@sourceforge.net]

Patches item #567468, was opened at 2002-06-11 09:28
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=305470&aid=567468&group_id=5470

Category: Demos and tools
Group: Python 2.3
Status: Closed
Resolution: Rejected
Priority: 6
Submitted By: Jason Merrill (jason_merrill)
Assigned to: Barry A. Warsaw (bwarsaw)
Summary: A different patch for python-mode vs gdb

Initial Comment:
Patch 509975 fixes the conflict between gdb-mode and
python-mode by checking whether the current process is
a python process.  My patch fixes it more simply, by
only clearing the overlay arrow if we were the ones who
set it.

I'd be happy with either patch.


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

Comment By: Nobody/Anonymous (nobody)
Date: 2002-07-16 10:02

Message:
Logged In: NO 

The problem my patch was intended to fix is that currently
just loading python-mode.el (as happens by default under Red
Hat 7.3) breaks gdb-mode.  With my patch, it works fine.

emacs only supports one overlay arrow at a time; if you hit
'next' in gdb, gdb-mode will set the overlay arrow, which
means that it will no longer be set in the python buffer. 
This may not be ideal behavior, but it's a limitation of
emacs, not a bug in my patch.

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

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-07-16 09:53

Message:
Logged In: YES 
user_id=12800

I've rejected 509975 because it doesn't play nice when
you're pdb tracking from the shell (see comments in that patch).

I'm not sure this patch works correctly either, but for a
different reason: it doesn't actually work for me!

If I add "import pdb; pdb.set_trace()" to a file and then
execute the file from the shell buffer, I see the overlay
arrow.  If I then switch to a gdb debugging a C program and
hit "next", the overlay arrow in the .py buffer disappears.

This seems like a tricky problem and I don't have a good
solution, but I think I have to reject this patch too.

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

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