Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

change handling of stepping into function that has no debug information #190

Open
ixje opened this issue May 10, 2023 · 0 comments
Open

Comments

@ixje
Copy link

ixje commented May 10, 2023

I think this is worthy of a discussion on how to handle this. Right now when trying to step into a function that has no debug symbols, the debugging will simply go to the first function it can find debug information for. To illustrate

def util_func(arg):
   return arg * 2

def call_inner():
   x = 1
   y = util_func(x)
   return y

def entry_point():
   call_inner()

Assume we have debug information for entry_point and util_func, but not for call_inner. We put a break point inside entry_point() on call_inner(). Now when trying to step into call_inner you'll actually end up in util_func instead. If you don't realize this is the logic then it can be quite confusing to end up in a function you don't expect.

I'm thinking we should at least give a warning about missing debug symbols and then maybe a choice what to do? Skip over or the current behaviour of first function it can find.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant