-
Notifications
You must be signed in to change notification settings - Fork 258
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
improvements for the disassembler #457
Conversation
8e65fcf
to
9c6cc0e
Compare
531cdda
to
27cf30a
Compare
a478cb4
to
d8e5806
Compare
123394a
to
46244df
Compare
46244df
to
6d5547c
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.
great stuff, but overall some changes are required
6d5547c
to
b6ad55d
Compare
Note: If possible it would be nice to have the Dissassembly Window be split, so the sizes of "source" vs. "assembly" can be adjusted. The later often has < 60 characters (at least with C, is that different with C++?), while the code is much wider. As it is now there is often a lot of empty space on the right side while the left has the code elided - and the user seems to not able to adjust these sizes. |
b6ad55d
to
256e21c
Compare
This comment was marked as resolved.
This comment was marked as resolved.
Nevermind, I've forgot the |
@milianw: Any chance to re-review? |
2ac1771
to
fbfaf33
Compare
there is now a magnifying glass and a checkbox for a case sensitive search |
fbfaf33
to
78b4fc7
Compare
The adjusted search works good. The only missing thing seems to be some visual feedback, maybe just select the line with the result? |
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.
Other than the "visual feedback" on the search and the minor README notes, I see no open points from a user-perspective.
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.
please write better commit messages
Just wondering: would it be more useful to split this PR into multiple parts? It solves multiple issues an it may be faster (or only more work, not sure) to get some implemented/fixed if the number of changes that need to be reviewed are smaller? |
78b4fc7
to
9ed3227
Compare
9ed3227
to
695a871
Compare
I removed the search stuff. This should now only contain reviewed code. |
Thank you very much! |
40a94ec
to
4256b03
Compare
If it isn't possible to re-review the reviewed code / merge that into master - could you please rebase the branch so the resulting appimage has both? |
Now the disassembler looks at symbol.actualPath and checks if that file exists (usualy located in .debug) If the file does not exists it searches in debugPaths and then in extraLibPaths If none is found it tries symbol.path (original lib file which may not include debug informations) fixes #450
closes #437 changes
Add a QSplitter to allow the user to customize the size of the views.
4256b03
to
bfc620e
Compare
done |
Thank you, the resulting AppImage works fine. Would it be reasonable to tackle #418 in this PR, too? That issue is about adding settings and use them in the disassembler view. |
|
This comment was marked as outdated.
This comment was marked as outdated.
Thank you for your work @lievenhey as always, and sorry for taking so long with this one! |
That seems to handle only binaries, from
but in any case that's something for another PR now :-) |
Now the disassembler looks at symbol.actualPath and checks if that file exists (usualy located in .debug)
If the file does not exists it searches in debugPaths and then in extraLibPaths
If none is found it tries symbol.path (original lib file which may not include debug informations)
fixes #450