bug#6097: 23.1; PDB should pop "up" the stack on return

bug#6097: 23.1; PDB should pop "up" the stack on return

[David Abrahams]

Please write in English if possible, because the Emacs maintainers
usually do not have translators to read other languages for them.

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

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

1) Debug a python program using PDB, say

    def g():
        pass

    def h():
        pass

    def f():
        g()
        h()

2) step into g()
3) hit `n' until you see

   --Return--

   in the *gud* buffer

4) Note that the GUD line marker is still pointing at the last line of g,
   just as it was before the last `n'

5) Hit `n' again.  Note that the GUD line marker is now pointing at
   the first line of h()

It would be more consistent and easier to use if, at step 4, the line
marker indicated the 3rd line of f(), i.e. the call to h()


If Emacs crashed, and you have the Emacs process in the gdb debugger,
please include the output from the following gdb commands:
    `bt full' and `xbacktrace'.
If you would like to further debug the crash, please read the file
/Applications/Emacs.app/Contents/Resources/etc/DEBUG for instructions.


In GNU Emacs 23.1.1 (i386-apple-darwin9.8.0, NS apple-appkit-949.54)
 of 2009-08-16 on black.local
Windowing system distributor `Apple', version 10.3.1038
configured using `configure  '--with-ns''

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: nil
  value of $XMODIFIERS: nil
  locale-coding-system: nil
  default-enable-multibyte-characters: t

Major mode: Emacs-Lisp

Minor modes in effect:
  shell-dirtrack-mode: t
  diff-auto-refine-mode: t
  show-paren-mode: t
  server-mode: t
  global-auto-revert-mode: t
  delete-selection-mode: t
  tooltip-mode: t
  mouse-wheel-mode: t
  menu-bar-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  font-lock-mode: t
  global-auto-composition-mode: t
  auto-composition-mode: t
  auto-encryption-mode: t
  auto-compression-mode: t
  line-number-mode: t
  transient-mark-mode: t

Recent input:
C-w C-s C-, C-, C-s l i n k s C-s C-s C-s C-s C-s C-s 
C-s C-s C-s C-n C-n C-p C-p C-p C-n C-n C-p C-p C-n 
C-n C-p C-x SPC C-x C-b C-x C-b C-x C-b b SPC p i p 
. i n d e x C-a C-k i m p o r t SPC p i p . i n d e 
x <return> C-x C-b C-x SPC C-x C-b C-x C-b C-x C-b 
M-p M-p M-n C-a M-d b C-e . P a c k a g e F i n d e 
r . _ _ i n i t _ _ <return> c <return> n <return> 
<return> <return> <return> <return> s <backspace> w 
h e r e <return> u <return> s <return> M-x f i n d 
- f u n <tab> <return> p d b <return> M-< C-n C-e C-n 
C-e C-, C-, C-, C-, C-, C-, C-s p d b C-s C-s C-s C-s 
C-s C-s C-s C-s C-s C-s C-s C-s C-s C-s C-s C-s C-s 
C-s C-s C-s C-s C-s C-s C-s C-s C-s C-s C-s C-s C-r 
C-r SPC s u p p C-r C-s C-s C-g M-< C-n C-n C-n C-n 
C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n 
C-n C-s p d b C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p 
C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p 
C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p 
C-n C-n C-p C-p C-p C-p C-s p y t h o n C-g C-p C-p 
C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p M-x r e p o 
r t - e m <tab> b u <tab> <return>

Recent messages:
pdbtrack: line 37, file /Users/dave/work/pipsync/int/pip/index.py
Mark set [2 times]
pdbtrack: line 142, file /Users/dave/work/pipsync/int/pip/commands/install.py
Mark set [2 times]
pdbtrack: line 708, file /Users/dave/work/pipsync/int/pip/req.py
uncompressing gud.el.gz...done
Mark set
Mark saved where search started
Mark set
Mark saved where search started
Quit

-- 
Dave Abrahams           Meet me at BoostCon: http://www.boostcon.com
BoostPro Computing
http://www.boostpro.com

bug#6097: 23.1; PDB should pop "up" the stack on return

[Stefan Kangas]

David Abrahams <dave@boostpro.com> writes:

> 1) Debug a python program using PDB, say
>
>     def g():
>         pass
>
>     def h():
>         pass
>
>     def f():
>         g()
>         h()
>
> 2) step into g()
> 3) hit `n' until you see
>
>    --Return--
>
>    in the *gud* buffer
>
> 4) Note that the GUD line marker is still pointing at the last line of g,
>    just as it was before the last `n'
>
> 5) Hit `n' again.  Note that the GUD line marker is now pointing at
>    the first line of h()
>
> It would be more consistent and easier to use if, at step 4, the line
> marker indicated the 3rd line of f(), i.e. the call to h()

I'm not exactly sure what you are requesting here.

To determine what line to jump to, pdb is parsing lines such as:

> /home/skangas/foo.py(2)g()->None
                       ^
> /home/skangas/foo.py(9)f()
                       ^

This works as expected on the latest master branch.

I'm not sure how we could do better here, unless pdb changes it's
output.  I'm therefore leaning towards closing this as notabug.

Please clarify if there is something I'm missing.

Best regards,
Stefan Kangas

bug#6097: 23.1; PDB should pop "up" the stack on return

[Stefan Kangas]

tags 6097 + notabug
close 6097
quit

Stefan Kangas <stefan@marxist.se> writes:

> I'm not sure how we could do better here, unless pdb changes it's
> output.  I'm therefore leaning towards closing this as notabug.
>
> Please clarify if there is something I'm missing.

No reply within 4 weeks, so I'm closing this bug now.

Best regards,
Stefan Kangas