Explore >> Select a destination
|
You are here 
|
www.gridbugs.org | ||
| | | | |
dataswamp.org
|
|
| | | | | Disclaimer I am not in any way an RE guru, I'm a software developer just like everybody else, but after learning about the "SNESticle" string on the Fight Night Round 2 ISO, I couldn't stop thinking a | |
| | | | |
jamchamb.net
|
|
| | | | | While looking for ways to activate the developer menus left over in Animal Crossing, including the NES emulator game selection menu, I found an interesting feature that exists in the original game that was always active, but never used by Nintendo. In addition to the NES/Famicom games that can be obtained in-game, it was possible to load new NES games from the memory card. I was also able to find a way to exploit this ROM loader to patch custom code and data into the game, allowing for code execution via the memory card. | |
| | | | |
ajxs.me
|
|
| | | | | A gentle introduction to reverse-engineering vintage synthesiser ROMs using the Ghidra disassembler. | |
| | | | |
jmmv.dev
|
|
| | | In a recent work discussion, I came across an argument that didn't sound quite right. The claim was that we needed to set up containers in our developer machines in order to run tests against a modern glibc. The justifications were that using LD_LIBRARY_PATH to load a different glibc didn't work and statically linking glibc wasn't possible either. But... running a program against a version of glibc that's different from the one installed on the system seems like a pretty standard requirement, doesn't it?... | ||
