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

Crash near 660fa4c40d #54

Open
Ranyaws opened this issue Oct 17, 2017 · 1 comment
Open

Crash near 660fa4c40d #54

Ranyaws opened this issue Oct 17, 2017 · 1 comment

Comments

@Ranyaws
Copy link

Ranyaws commented Oct 17, 2017

sudo ./sifter.py --unk --dis --len --sync --tick --save -- -P1 -t -i 660fa4c40d0000000000000000000000

image

If I unpause the program will crash to commandline faster than I can can see.
In my first run which took almost 4 hours it ended up probably at this exact moment too, maybe already before that though, since there was some weird stuff going on in the few seconds before the crash.

I since I didn't use the --save command I tried botching a resume file and I got some overflow error that looked funny so I renamed the data-folder to give the program a fresh start.

Core i5 3450.
I guess there is some instruction here that ends up crashing it.

@rigred
Copy link

rigred commented Oct 20, 2017

You can try blacklisting this instruction or skip the range by using the command line parameters.

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

2 participants