You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The break_next_call function which steps through the execution has this functionality that it can stop on a target symbol checked via a regular expression.
However, both the regular expression as well as the string provided to it are constructed on each loop iteration (!). While Python regexes are cached internally, we should not rely on this functionality.
This commit changes `break_next_call` so it compiles the symbol regex
once, but also it changes the regex so that we do not append `$` at the
end of it.
The appending of `$` was counter-intuitive imho and it was never said to
the user that this happens.
The
break_next_call
function which steps through the execution has this functionality that it can stop on a target symbol checked via a regular expression.However, both the regular expression as well as the string provided to it are constructed on each loop iteration (!). While Python regexes are cached internally, we should not rely on this functionality.
pwndbg/pwndbg/gdblib/next.py
Lines 107 to 113 in e37591b
Effectively, this issue is just about doing something like:
The text was updated successfully, but these errors were encountered: