all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Syver Enstad <syver.enstad@cisco.com>
To: 6098@debbugs.gnu.org
Subject: bug#6098: Fix for broken breakpoint handling in gud pdb
Date: Fri, 18 Mar 2011 18:03:07 +0100	[thread overview]
Message-ID: <4D83904B.8010501@cisco.com> (raw)
In-Reply-To: <m2wrvjsnx3.fsf@boostpro.com>

Patch for gud.el version 23.1 line 1636

The point of this patch is to give pdb full paths so that one can set 
breakpoints
in files outside the current directory.

This is acheived by addding the %d specification to the command.


--- /tmp/original.el    2011-03-18 17:55:30.131681523 +0100
+++ /tmp/improved.el    2011-03-18 17:55:14.870401366 +0100
@@ -1633,8 +1633,8 @@
    (gud-common-init command-line nil 'gud-pdb-marker-filter)
    (set (make-local-variable 'gud-minor-mode) 'pdb)

-  (gud-def gud-break  "break %f:%l"  "\C-b" "Set breakpoint at current 
line.")
-  (gud-def gud-remove "clear %f:%l"  "\C-d" "Remove breakpoint at 
current line")
+  (gud-def gud-break  "break %d%f:%l"  "\C-b" "Set breakpoint at 
current line.")
+  (gud-def gud-remove "clear %d%f:%l"  "\C-d" "Remove breakpoint at 
current line")
    (gud-def gud-step   "step"         "\C-s" "Step one source line with 
display.")
    (gud-def gud-next   "next"         "\C-n" "Step one line (skip 
functions).")
    (gud-def gud-cont   "continue"     "\C-r" "Continue with display.")






  reply	other threads:[~2011-03-18 17:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-04 15:10 bug#6098: 23.1; gud-break doesn't deal with Python modules David Abrahams
2011-03-18 17:03 ` Syver Enstad [this message]
2012-01-29  7:07   ` bug#6098: Fix for broken breakpoint handling in gud pdb Chong Yidong
2012-03-14 18:49 ` bug#6098: Someone obviously tried to fix this upstream Dave Abrahams
2012-03-14 20:41   ` Andreas Schwab

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D83904B.8010501@cisco.com \
    --to=syver.enstad@cisco.com \
    --cc=6098@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.