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

Kill the _end section flags and fix flag size #11349

Merged
merged 1 commit into from
Sep 13, 2018
Merged

Kill the _end section flags and fix flag size #11349

merged 1 commit into from
Sep 13, 2018

Conversation

radare
Copy link
Collaborator

@radare radare commented Sep 2, 2018

Fix #11348

@radare radare added this to the 3.0 milestone Sep 2, 2018
@radare
Copy link
Collaborator Author

radare commented Sep 2, 2018

the XX look good to me, updating them should be harmless. Also noticed some improvements.
screen shot 2018-09-02 at 03 24 27

Copy link
Contributor

@ret2libc ret2libc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ret2libc
Copy link
Contributor

ret2libc commented Sep 3, 2018

of course after fixing tests :D

@radare
Copy link
Collaborator Author

radare commented Sep 3, 2018 via email

@kazarmy
Copy link
Contributor

kazarmy commented Sep 10, 2018

Some people are going to miss those _end flags since:

  1. The alternative of section..<section> + $s{section..<section>} is less convenient.
  2. It would be nice to have a visual indicator of the section you're entering when moving backwards in Visual mode.

Regarding the above, it might be better to have an asm config var to show all flags at an address.

@ret2libc
Copy link
Contributor

It would be nice to have a visual indicator of the section you're entering when moving backwards in Visual mode.

that's true, though I think things should be displayed based on flag starting address + flag size, instead of having two flags as it is right now in master.

@kazarmy
Copy link
Contributor

kazarmy commented Sep 11, 2018

might be tricky to implement efficiently but ok

@radare
Copy link
Collaborator Author

radare commented Sep 13, 2018

because i think its easier to improve the RNumCallback to handle $$flagname for this

[0x100001200]> ?v $$section.2.__TEXT.__stub_helper
0x100004900
[0x100001200]> ?v section.2.__TEXT.__stub_helper
0x1000045f8
[0x100001200]>

i have a bunch of suggestions and ideas to improve the syntax for those numbers

@radare
Copy link
Collaborator Author

radare commented Sep 13, 2018

moved to $e{}

[0x100001200]> ?v section.0.__TEXT.__text
0x100000f20
[0x100001200]> ?v $e{section.0.__TEXT.__text}
0x10000442e
[0x100001200]> ?v $s{section.0.__TEXT.__text}
0x350e
[0x100001200]>

@radare
Copy link
Collaborator Author

radare commented Sep 13, 2018

the _end flags introduce issues in disasm because it takes the _end instead of the next begin one and such, which use cases do people have for the _end flags? because i think with that $e{} is enough

@Maijin
Copy link
Contributor

Maijin commented Sep 13, 2018

The e{} Sgtm

@XVilka
Copy link
Contributor

XVilka commented Sep 13, 2018 via email

@radare
Copy link
Collaborator Author

radare commented Sep 13, 2018

ok, rebasing and updating tests for the glory of the merge

@radare
Copy link
Collaborator Author

radare commented Sep 13, 2018

before adding this to the book i would prefer to discuss all the ?$? vars

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

Successfully merging this pull request may close these issues.

None yet

5 participants