This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: make python-mode play nice with gdb
Type: Stage:
Components: Demos and Tools Versions: Python 2.3
process
Status: closed Resolution: rejected
Dependencies: Superseder:
Assigned To: barry Nosy List: alex_coventry, barry
Priority: normal Keywords: patch

Created on 2002-01-29 01:32 by alex_coventry, last changed 2022-04-10 16:04 by admin. This issue is now closed.

Files
File name Uploaded Description Edit
python-mode.el.diff alex_coventry, 2002-02-03 21:18
Messages (3)
msg38808 - (view) Author: Alex Coventry (alex_coventry) Date: 2002-01-29 01:32
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
msg38809 - (view) Author: Alex Coventry (alex_coventry) Date: 2002-02-03 21:18
Logged In: YES 
user_id=49686

sorry, somehow failed to include the diff :)
msg38810 - (view) Author: Barry A. Warsaw (barry) * (Python committer) Date: 2002-07-16 16:43
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.
History
Date User Action Args
2022-04-10 16:04:55adminsetgithub: 35991
2002-01-29 01:32:09alex_coventrycreate