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

Display hangs partway through #44

Open
killerkalamari opened this issue Sep 10, 2017 · 6 comments
Open

Display hangs partway through #44

killerkalamari opened this issue Sep 10, 2017 · 6 comments

Comments

@killerkalamari
Copy link

killerkalamari commented Sep 10, 2017

Displayed fine for a while, then stopped at 2e0f9a5be2. CPU usage remains at 100%. I can manually check the data/sync contents and I continue to see changes, so the program isn't hung, but the display remains constant.

Screenshot:
hang at 2e0f9a5be2

Command:
sudo ./sifter.py --unk --dis --len --sync --tick -- -P1 -t

Code is from the rigred branch: https://github.com/rigred/sandsifter-tests
CPU: Intel i7-4790K
OS: Ubuntu MATE 16.04 LTS
libcapstone3, libcapstone3-dev, python-capstone: 3.0.4-0.2
Terminal: MATE Terminal 1.12.1-1

@rigred
Copy link

rigred commented Oct 1, 2017

I just noticed this issue. Is this still occurring on the current version too?
I haven't seen it occur myself yet, but there are a number of other problems.

@Xiretza
Copy link

Xiretza commented Oct 1, 2017

There isn't really a "current version", this repo only has one commit.

@rigred
Copy link

rigred commented Oct 1, 2017

Sorry I was talking about my fork which fixes a number of issues: https://github.com/rigred/sandsifter

@killerkalamari
Copy link
Author

Despite the display issue it seems like it ran to completion and eventually started displaying things in what looked like a review of findings. I didn't try to run it twice.

@killerkalamari
Copy link
Author

Sorry for the confusion regarding the fork. I would have opened the bug there, but it did not seem to be an option.

@rigred
Copy link

rigred commented Oct 1, 2017

Thanks for telling me. Silly me forgot to enable issues.
I've just noticed it and enabled that.

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

No branches or pull requests

3 participants