volatile int blackhole;
blackhole = 1;
const int X = blackhole;
const int Y = blackhole;
Compiler is forbidden to assume that X == 1 would be true. It's also forbidden to assume that X == Y. const just means the address and/or the data at the address is read only. const volatile int* const hwreg; -> "read only volatile value at read only address hwreg". Compiler can assume the hwreg address won't magically change, but can't assume the value read from that address won't.
Holy cow.
gdb> break before it crashes
gdb> record full
gdb> continue
(segfault)
gdb> set exec-direction reverse
I clicked the link with SUS knob set to 900% and the other hand on the main breaker. It did not disappoint.
Tätä odottaessa, kosmos24.
GameBoy Color with a single game: Pokémon Red.
Next time I was able go to the shop they had upgraded to GameBoy Advance and no GB/GBC games were to be never found again. It was the best/worst thing I ever got. :'(
Please, never run plain "sudo make install" on a package managed system. With linux from scratch it might make sense... Doing so will "install" the thing (copy the files), but the copied files are foreign to the package manager. You cannot easily undo this, and can cause issues in future.
You had a compiler error about missing header file, libXft is from Xorg project. "devel" versions of packages usually provide these files.
st is from suckless project so it doesn't need much to be "installed": copy the built binaries into ~/bin/ or /opt/ and set your user PATH to look into those dirs. Check your user env if you need to modify the PATH.
I'm considering to replace the TIM (repasting) + thermal pads at some point... The card is now ~5 years old, and if the paste goes bad that would be end of it. The dust that all boards accumulate overtime is also a risk factor of how long components last.
Me:
- Need to debug a program
- Debugger doesn't work
- Need to debug the debugger
- ...
- Look at a hardware bug in the CPU that breaks ptrace syscall /s
- Go find a bucket of sand.