bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

gud/pdb gud-remove fails on python > ver 1.5.1


From: Syver Enstad
Subject: gud/pdb gud-remove fails on python > ver 1.5.1
Date: 17 Sep 2002 17:29:56 +0200
User-agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2

This bug report will be sent to the Free Software Foundation,
not to your local site managers!
Please write in English, because the Emacs maintainers do not have
translators to read other languages for them.

Your bug report will be posted to the address@hidden mailing list,
and to the gnu.emacs.bug news group.

In GNU Emacs 21.2.1 (i386-msvc-nt5.0.2195)
 of 2002-04-01 on TECH
configured using `configure --with-msvc (12.00)'
Important settings:
  value of $LC_ALL: nil
  value of $LC_COLLATE: nil
  value of $LC_CTYPE: nil
  value of $LC_MESSAGES: nil
  value of $LC_MONETARY: nil
  value of $LC_NUMERIC: nil
  value of $LC_TIME: nil
  value of $LANG: no_NO
  locale-coding-system: iso-latin-1
  default-enable-multibyte-characters: t

Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:

The command gud-remove is under pdb (in gud.el) is wrong for versions
of python after 1.5.1. It is defined like this:
  (gud-def gud-remove "clear %l"   ......) line 1404 in gud.el

Which removes the %l nth break point defined instead of breakpoint at
line %l.

I have tested with a new definition:
(gud-def gud-remove "clear %f:%l" .....) line 1404 in gud.el
which works fine on my machine (and I see no reason that it won't on
anybody else's either).

Here is the citation from the pdb manual that explains the bug:

cl(ear) filename:lineno
cl(ear) [bpnumber [bpnumber...]]

Note that the argument is different from previous versions of
the debugger (in python distributions 1.5.1 and before) where
a linenumber was used instead of either filename:lineno or
breakpoint numbers.

PS: I think there are very few pythonistas who still use the 1.5.1 version
of python.



-- 

Vennlig hilsen 

Syver Enstad






reply via email to

[Prev in Thread] Current Thread [Next in Thread]