make python-mode play nice with gdb

[daee6a4b-3224-41bd-8850-ba9ee815ae20]

BPO	509975
Nosy	@warsaw
Files	python-mode.el.diff

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields: ```python assignee = 'https://github.com/warsaw' closed_at = created_at = labels = [] title = 'make python-mode play nice with gdb' updated_at = user = 'https://bugs.python.org/alexcoventry' ``` bugs.python.org fields: ```python activity = actor = 'barry' assignee = 'barry' closed = True closed_date = None closer = None components = ['Demos and Tools'] creation = creator = 'alex_coventry' dependencies = [] files = ['3926'] hgrepos = [] issue_num = 509975 keywords = ['patch'] message_count = 3.0 messages = ['38808', '38809', '38810'] nosy_count = 2.0 nosy_names = ['barry', 'alex_coventry'] pr_nums = [] priority = 'normal' resolution = 'rejected' stage = None status = 'closed' superseder = None type = None url = 'https://bugs.python.org/issue509975' versions = ['Python 2.3'] ```

[daee6a4b-3224-41bd-8850-ba9ee815ae20]

if you run gdb (and presumably other debuggers) while python-mode is loaded, the little arrow it uses to indicate the current position in the source code fails to appear. this is because the comint hook py-pdbtrack-track-stack-file wipes it out regardless of whether the current buffer process comes from python.

hth. alex

[daee6a4b-3224-41bd-8850-ba9ee815ae20]

Logged In: YES user_id=49686

sorry, somehow failed to include the diff :)

[warsaw]

Logged In: YES user_id=12800

This patch doesn't work for a use case that I've found to be very common, namely adding "import pdb ; pdb.set_trace()" in the code where you want to start tracing, and then just running the program from the shell buffer.

Ken turned me on to this idiom and it's really powerful. The test for process-command matching exactly py-python-command or py-jpython-command breaks this.

I'm not sure patch 567468 is much better, but for different reasons.