-
Notifications
You must be signed in to change notification settings - Fork 71
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
Fail to run it. #11
Comments
@JulianLai what the following command returns: "cat /proc/kallsyms | grep sys_call_table"? could you please also share the backtrace from gdb? |
|
./meltdown_checker |
Hi @sidro. I'll find a way to fall back to a different approach when those files aren't usable. Thanks! |
@sidro: do you have /boot mounted? could you please try running the program as root instead? |
@JulianLai: this commit 9b74046 may help you, please pull changes and try again |
@raphaelsc , commit 9b74046 did not help here; I get similar errors as posted by @sidro in my case /boot is mounted: |
thanks for the report @sergiy-kozak. i'll work on fixing that ASAP. |
Not sure what else I can provide, that is what I tried to display more info with gdb: $ gdb ./meltdown-checker Program received signal SIGABRT, Aborted. |
@sergiy-kozak could u pls consider running it as root? that will give me direction |
Tried it, doesn't look different though: [root@arch-dt-skozak]: /home/skozak/git-public/Am-I-affected-by-Meltdown># gdb ./meltdown-checker Program received signal SIGABRT, Aborted. Value of kptr_restrict: Kernel (Arch linux LTS kernel): |
The text was updated successfully, but these errors were encountered: