unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: npostavs@users.sourceforge.net
To: Live System User <nyc4bos@aol.com>
Cc: 25194@debbugs.gnu.org
Subject: bug#25194: 25.1; Python debugger breakpoint error
Date: Sun, 01 Jan 2017 23:35:40 -0500	[thread overview]
Message-ID: <87d1g66pur.fsf@users.sourceforge.net> (raw)
In-Reply-To: <87zijz7o9m.fsf@aol.com> (Live System User's message of "Tue, 13 Dec 2016 12:05:41 -0500")

tags 25194 unreproducible
quit

Live System User <nyc4bos@aol.com> writes:
>
>   I never used this command before -- so I tried it:
>
>      M-x debug-on-entry RET gud-break
>
>      When trying to set a breakpoint, I got a *Backtrace*:
>
> Debugger entered--Lisp error: (wrong-type-argument stringp nil)
>   file-name-directory(nil)
>   gud-format-command("break %d%f:%l" 4)

It looks like buffer-file-name-localized in gud-format-command is nil
for you, though I don't see how that's possible and I can't reproduce
this here.

(defun gud-format-command (str arg)
  (let ((insource (not (eq (current-buffer) gud-comint-buffer)))
        (frame (or gud-last-frame gud-last-last-frame))
        (buffer-file-name-localized
         (and (buffer-file-name)
              (or (file-remote-p (buffer-file-name) 'localname)
                  (buffer-file-name))))
    ...
         ((eq key ?d)
          (setq subst (file-name-directory (if insource
                                               buffer-file-name-localized
                                             (car frame))))





      reply	other threads:[~2017-01-02  4:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-13 10:10 bug#25194: 25.1; Python debugger breakpoint error Live System User
2016-12-13 11:46 ` Andreas Röhler
2016-12-13 12:25   ` Live System User
2016-12-13 16:08     ` Andreas Röhler
2016-12-13 15:44 ` Live System User
2016-12-13 16:06 ` Eli Zaretskii
2016-12-13 17:05   ` Live System User
2017-01-02  4:35     ` npostavs [this message]

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=87d1g66pur.fsf@users.sourceforge.net \
    --to=npostavs@users.sourceforge.net \
    --cc=25194@debbugs.gnu.org \
    --cc=nyc4bos@aol.com \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).