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
Display jumping fix useless decompilation #2351
Display jumping fix useless decompilation #2351
Conversation
8217b5b
to
5e34acb
Compare
duplicate code exists in some places, I have to take care of them.
cleaning up of comments left
ef14282
to
e1775ef
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I sometimes noticed a situation where I select a line in decompiler, add a breakpoint and breakpoint appears in disassembly but not the decompiler. It's hard to tell if it's an actual problem or just r2ghidra returning bad offset<->line mapping.
Does this PR is using functionalities from the decompiler-refactoring? if not, maybe this can be pushed to maste as it is a bug-fix\improvement which is small and can be enjoyed by our users. What do you think? |
@ITAYC0HEN Yes, we have improved "DecompilerWidget" and this uses some improvements and features in decompiler-refactoring (e.g. |
Thanks! <3 |
* save scroll position and reset to that if the newly decompiled function is the same as the previous one * emit instructionChanged signal replaced completely by breakpointsChanged in toggle/add breakpoint functions. * removed addbreakpoint(QString) and toggleBreakpoint(QString)
* save scroll position and reset to that if the newly decompiled function is the same as the previous one * emit instructionChanged signal replaced completely by breakpointsChanged in toggle/add breakpoint functions. * removed addbreakpoint(QString) and toggleBreakpoint(QString)
* save scroll position and reset to that if the newly decompiled function is the same as the previous one * instructionChanged signal replaced completely by breakpointsChanged in toggle/add breakpoint functions. * removed addbreakpoint(QString) and toggleBreakpoint(QString)
* save scroll position and reset to that if the newly decompiled function is the same as the previous one * instructionChanged signal replaced completely by breakpointsChanged in toggle/add breakpoint functions. * removed addbreakpoint(QString) and toggleBreakpoint(QString)
* save scroll position and reset to that if the newly decompiled function is the same as the previous one * instructionChanged signal replaced completely by breakpointsChanged in toggle/add breakpoint functions. * removed addbreakpoint(QString) and toggleBreakpoint(QString)
* save scroll position and reset to that if the newly decompiled function is the same as the previous one * instructionChanged signal replaced completely by breakpointsChanged in toggle/add breakpoint functions. * removed addbreakpoint(QString) and toggleBreakpoint(QString)
* save scroll position and reset to that if the newly decompiled function is the same as the previous one * instructionChanged signal replaced completely by breakpointsChanged in toggle/add breakpoint functions. * removed addbreakpoint(QString) and toggleBreakpoint(QString)
* save scroll position and reset to that if the newly decompiled function is the same as the previous one * instructionChanged signal replaced completely by breakpointsChanged in toggle/add breakpoint functions. * removed addbreakpoint(QString) and toggleBreakpoint(QString)
Your checklist for this pull request
Detailed description
The important modifications and additions in this PR are:
breakpointsChanged()
tobreakpointsChanged(RVA offset)
. Removedemit instructionChanged
from all functions that emitbreakpointsChanged
.Display jumps while toggling breakpoint (Before)
Display position doesn't change while toggling breakpoint (After)
You can notice the same change in other actions also, e.g. Add/Rename/Remove names, Refresh, Add/Delete/Modify comments, etc.
Test plan (required)
je address
tojne address
and see if the display changes in an undesirable way.Closing issues
closes #2270