How I Fixed a 10 Year Old Guitar Hero Bug Without the Source Code
Channel:ExileLord · Length:12:09 · Published:2017-09-24 · Views:403967
Summary
A reverse engineer walks through fixing a ten-year-old bug in Guitar Hero III without access to its source code, using a disassembler and decompiler. It is technical but explained step by step.
Why HN recommends it
Held up as a favorite tech talk and a great hard-debugging story about patching a game binary.
One of the best though, for me, has to be this one on fixing a Guitar Hero bug — HN, 2017
Testing, debugging & developer tools · Security & hacking · Speedrunning, glitches & game hacking
Subtitles (excerpt)
one of the problems that's playing the guitar hero 3 community for a while is that there's a limit to the amount of songs you can have on any given set list if you're an avid player of customs you'd probably run into this bug in the past if you go over the lower end of the limit the game will crash when selecting a song if you go over the upper end of the limit the game will crash when switching to the setlist even stranger though is that over time the maximum amount of songs the setlist can hold seems to shrink eventually the game will just crash when a song that setlist to selected even if it worked fine just moments ago the only fix the community has has been to remove songs from the setlist the primary tool I'm going to be using is hex Ray's interactive disassembler or Ida I don't have the source code for Guitar Hero 3 so I have to use I had to figure out what the game's code is actually doing I've already done a lot of work on Guitar Hero 3 which will make my job easier since I'm not starting from scratch so let's start well the game is loading I attach a debugger using either now when the game crashes I can take control of it and see what's going on [Music] so it looks like we're looking at a null pointer
On Hacker News
I put a bunch of the ones I enjoyed here: [LINK] One of the best though, for me, has to be this one on fixing a Guitar Hero bug: [VIDEO] — zapperdapper, 2017-12
This video[1] on reverse-engineering parts of Guitar Hero 3 covers a few similar techniques that were used to heavily obfuscate the game code that you might find interesting. [1] [VIDEO] — 0xC0ncord, 2025-01
You reminded me of this: "How I Fixed a 10 Year Old Guitar Hero Bug Without the Source Code" [VIDEO] — Tempest1981, 2018-11
Related videos
- The world depends on a collection of strange items. They're not cheap · Veritasium · 18:32
- RailsConf 2014 - All the Little Things by Sandi Metz · Confreaks · 38:47
- SM64 - Watch for Rolling Rocks - 0.5x A Presses (Commentated) [OUTDATED] · pannenkoek2012 · 24:38
- Reverse emulating the NES to give it SUPER POWERS! · suckerpinch · 22:21
- "Testing Distributed Systems w/ Deterministic Simulation" by Will Wilson · Strange Loop Conference · 40:20
- Behind the Scenes of iOS Security · Black Hat · 51:31
- 🚀 TDD, Where Did It All Go Wrong (Ian Cooper) · DevTernity Conference · 1:03:55
- Bret Victor - Inventing on Principle · Rui Oliveira · 54:20
- Why Electronic Voting Is Still A Bad Idea · Tom Scott · 12:00
- Solving Problems the Clojure Way - Rafal Dittwald · Clojure/north · 1:02:26
- Debugging Under Fire: Keep your Head when Systems have Lost their Mind • Bryan Cantrill • GOTO 2017 · GOTO Conferences · 52:34
- "Performance Matters" by Emery Berger · Strange Loop Conference · 42:15
- USENIX Security '18-Q: Why Do Keynote Speakers Keep Suggesting That Improving Security Is Possible? · USENIX · 51:22
- Defcon 18 Changing threats to privacy Moxie Marlinspike Part · killab66661 · 42:50
- A Tour of the Acme Editor · Russ Cox · 23:16
- MarI/O - Machine Learning for Video Games · SethBling · 5:57