From: Live System User <nyc4bos@aol.com>
To: 25194@debbugs.gnu.org
Subject: bug#25194: 25.1; Python debugger breakpoint error
Date: Tue, 13 Dec 2016 10:44:27 -0500 [thread overview]
Message-ID: <874m2796lg.fsf@aol.com> (raw)
In-Reply-To: <87k2b487ic.fsf@aol.com>
Andreas Röhler <andreas.roehler@easy-emacs.de> writes:
> On 13.12.2016 11:10, Live System User wrote:
>> Hi,
>>
>> When trying to debug a Python program, I get the following
>> error when trying to set a breakpoint:
>>
>> 0. emaccs -Q &
>>
>> 1. C-x C-f test.py
>>
>> 2. From the menubar: Python->Debugger
>>
>> Run pdb (like this): python -m pdb test.py
>>
>> 3. Click on "Next Line" so I can see a source line
>>
>> 4. Cick on "Set Breakpoint"
>>
>> I now get the error:
>> Wrong type argument: stringp, nil
>>
>> Turning on `debug-on-error' yields the same results.
>> However, on the *Messages* buffer there is a little more
>> information about the error:
>>
>> gud-format-command: Wrong type argument: stringp, nil
>>
>> How does one debug this problem further?
>>
>> Thanks.
>>
[...]
>
> Here it works calling just
>
> pdb test.py
>
> not "python -m"before
Normally, `pdb' is just a shell script (or an alias) that
calls/execs the Python debugger containing something like:
exec python -m pdb $1 $2 $3 $4 $5 $6 $7 $8 $9
So invoking "python -m test.py" from the prompt is equalivant
and I can ust the commands (LIST, NEXT, etc) all the same.
The problem I am having is setting breakpoints.
Thanks.
next prev parent reply other threads:[~2016-12-13 15:44 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 [this message]
2016-12-13 16:06 ` Eli Zaretskii
2016-12-13 17:05 ` Live System User
2017-01-02 4:35 ` npostavs
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=874m2796lg.fsf@aol.com \
--to=nyc4bos@aol.com \
--cc=25194@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 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).