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

Feature: database.marks needs a matcher class since it's a filterable list #11

Open
arizvisa opened this issue Sep 23, 2018 · 2 comments

Comments

@arizvisa
Copy link
Owner

Most list-like things in ida-minsc expose a matcher class along with a number of keywords that can be used to filter their contents. database.marks is another one of those namespaces but for some reason it's missing a matcher class in order to filter it. The reason for this might be that the number of marks that IDA allows for you to create in a database is limited (I think 64?).

Nonetheless, it doesn't hurt to implement database.marks.list, database.marks.iterate, and database.marks.search like all of the other searchable namespaces. This will require implementing a matcher class for it and maybe a few keywords to filter each individual mark.

@arizvisa
Copy link
Owner Author

For the record, I just don't use marks anymore. They're too limited.

@arizvisa
Copy link
Owner Author

Haven't made any progress on this because their maximum number (16) is just too limited. This will probably get added once I start moving the matchers into their own module.

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

No branches or pull requests

1 participant