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

Add RzBaseFindOpt for custom thread status callback #2768

Merged
merged 5 commits into from
Jul 6, 2022
Merged

Conversation

wargio
Copy link
Member

@wargio wargio commented Jul 2, 2022

Your checklist for this pull request

  • I've read the guidelines for contributing to this repository
  • I made sure to follow the project's coding style
  • I've documented or updated the documentation of every function and struct this PR changes. If not so I've explained why.
  • I've added tests that prove my fix is effective or that my feature works (if possible)
  • I've updated the rizin book with the relevant information (if needed)

Detailed description

Add RzBaseFindOpt to allow to have custom thread status callbacks

@wargio wargio changed the title Add RzBaseFindOpt to allow to have custom thread status callbacks Add RzBaseFindOpt for custom thread status callback Jul 3, 2022
Copy link
Member

@XVilka XVilka left a comment

Choose a reason for hiding this comment

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

Looks good, but it would also benefit from unit/integration test, I think.

Comment on lines 27 to 29
ut64 begin_address; ///< Thread begin address
ut64 current_address; ///< Thread current address
ut64 end_address; ///< Thread end address
Copy link
Member

Choose a reason for hiding this comment

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

What is the "thread begin address'?

Copy link
Member Author

Choose a reason for hiding this comment

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

each thread has a range to scan, that is the thread range

Copy link
Member

Choose a reason for hiding this comment

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

ok maybe be a bit more explicit about this in the doc for these fields.

Moreover, from a more high level point of view, why do we care about the details? I mean, do we really need to export the information about threads running the search? Are you planning to export this info in cutter?

Copy link
Member Author

Choose a reason for hiding this comment

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

yes.

Copy link
Member

@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

test/unit/test_basefind.c Outdated Show resolved Hide resolved
@wargio wargio merged commit 2e0d490 into dev Jul 6, 2022
@wargio wargio deleted the basefind-cutter-api branch July 6, 2022 09:34
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.

3 participants