I have been trying to follow along but I'm confused why anything happens.
There's a test button that calls ThreadProc_dbg(bug) which then calls test(result), which in turns has some assembler code commented out and finishes with:
unescape('%u31C9%u5589%uE55D%u2EF8%uC390%u9090');
return 0;
The variable 'result' is (visibly) untouched by the function but ThreadProc_dbg tests its value to see if the processor is vulnerable or not. So just the test() function has the good stuff. (assuming it works) So either the assembler code does something even though it's commented out, or the unescape is not happy but I'm not sure why…I haven't tried too much on the code that actually crashing the computer (or whatever it does) since just the test puzzles me.