Step into subroutine call, but not calls made for parameters

Question

func(a(), b.c)

When executing the line above in the pdb debugger, using step will actually step into a, and then into the getter for b.c if its atypical (such as being a property), before actually stepping into func.

Generally I find myself using step followed by r to return from the frames I'm not interested in, and often inexplicably pass over and miss the opportunity to step directly into func.

How do I step directly into func, or what sequence of debugger commands will guarantee that I end up in func rather than passing over it?

Alex Martelli · Accepted Answer · 2010-07-17 03:53:26Z

2

tb func ("temporary break at func") followed by c ("continue") should work.

answered Jul 17, 2010 at 3:53

Alex Martelli

887k175 gold badges1.3k silver badges1.4k bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Vicki Laidler · Accepted Answer · 2010-07-17 03:55:04Z

0

I would handle this by setting a break at the line number inside func that you're interested in, and then use continue. For example suppose your code looks like this:

110  def func(a1, a2):
111      "" docstring ""
112      first interesting line

then do this:

python -m pdb caller.py
pdb> b 112
pdb> c

answered Jul 17, 2010 at 3:55

Vicki Laidler

3,4892 gold badges22 silver badges18 bronze badges

1 Comment

Alex Martelli Over a year ago

This leaves a break at that line -- tbreak (the temporary break, that works just once), as I suggested earlier, seems closer to what the OP is asking.

Collectives™ on Stack Overflow

Step into subroutine call, but not calls made for parameters

2 Answers 2

Comments

1 Comment

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest

Linked

Related