fix(debugging_utils): do not default to hex for offsets - #301
Open
c0rydoras wants to merge 1 commit into
Open
Conversation
with this, `+0x123` does what `+123` did before, and `+123` is actually `+123` and not `+291`
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Currently, setting a breakpoint at
func+123breaks atfunc.address + 0x123, which is somewhat uninituitive/unexpectedBy changing
int(offset, 16)toint(offset, 0),+0x123will work continue working as before, but+123will be123(decimal) instead of291see https://docs.python.org/3/library/functions.html#int for details on
int(N, 0)