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

Strings view does not load all strings sometimes #2796

Closed
thisusernameistaken opened this issue Dec 21, 2021 · 3 comments
Closed

Strings view does not load all strings sometimes #2796

thisusernameistaken opened this issue Dec 21, 2021 · 3 comments
Assignees
Labels
Type: Bug Issue is a non-crashing bug with repro steps
Milestone

Comments

@thisusernameistaken
Copy link

Binary Ninja Version
2.4.3108-dev

Describe the bug
When loading a bndb saved for a larger binary (150mb+), only a few strings appear in the strings view or in bv.get_strings. The only way I've noticed to get them to appear is to reanalyze the entire binary, which can take a long time on these larger binaries, or press "a" on a string. Pressing "a" on a string seems to analyze around 2097000 byte chunks at a time, so to get all the strings to load, I have to constantly press "a" on a string a ton of times. After saving the bndb again with all the strings loaded and reopening the bndb, the strings are gone again and I have to repeat the process.

To Reproduce
Steps to reproduce the behavior:

  1. Open a bndb of a large binary
  2. View strings window and see only a fraction of the strings loaded
  3. Press "a" on a string and see a chunk of strings added to the strings view, but not all of them

Expected behavior
When opening a bndb, all the strings in the binary should appear in the strings window

Version and Platform (required):

  • Binary Ninja: Dev 2.4.3108
  • OS: Ubuntu Linux
  • Version 20.04
@thisusernameistaken thisusernameistaken changed the title Strings view Strings view does not load all strings sometimes Dec 21, 2021
@plafosse plafosse added the Type: Bug Issue is a non-crashing bug with repro steps label Jan 10, 2022
@plafosse plafosse self-assigned this Jan 10, 2022
@plafosse
Copy link
Member

thanks I think I have a fix for this issue. Hopefully it will be pushed out today.

@plafosse plafosse added this to the 3.0 milestone Jan 24, 2022
@plafosse
Copy link
Member

Fixed in 2.5.3190

@hanssl
Copy link

hanssl commented Feb 7, 2022

I am seeing this same bug on 3.0.3233 for small binaries.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Issue is a non-crashing bug with repro steps
Projects
None yet
Development

No branches or pull requests

3 participants