GNU bug report logs - #25194
25.1; Python debugger breakpoint error

Previous Next

Full log

Message #14 received at 25194 <at> debbugs.gnu.org (full text, mbox):

From: Live System User <nyc4bos <at> aol.com>
To: 25194 <at> debbugs.gnu.org
Subject: 25.1; Python debugger breakpoint error
Date: Tue, 13 Dec 2016 10:44:27 -0500

Andreas Röhler <andreas.roehler <at> 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.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.