NOTICE: If you don't know what a gdbstub or debugger is or how to debug/reverse engineer, then this post isn't for you. This will not help you play Pokemon or any other game so don't ask, please. Kind of a release thread I guess? This may or may not be very useful depending on what game you are working on, but I spent the past 2 and a half months working on a gdbstub for Citra that finally got merged into master 2 days ago. This is what I spent my free time on after releasing Labyrinth no Kanata and Nanashi no Game: Me. Having a gdbstub was on the list of features the Citra devs wanted since it would make it easier to debug some games, but my personal goal was to be able to reverse engineer 3DS games for fan translations in the same way that I do for DS games (using DeSmuME's gdbstub and IDA Pro). Especially when I was working on Labyrinth no Kanata, something like this would have helped greatly in trying to fix some things (Labyrinth no Kanata wasn't really even playable in Citra while I was making the fan translation, though. It is now, though! Sorta). So what can this do? - Debug, in real time, a game's code as it is being executed in Citra - Breakpoints - Step code - View, modify memory - View, modify registers - You can use any gdb client to connect to the gdbserver. That means you can use a plain ol' gdb.exe or something like IDA Pro or anything in between (as long as it supports ARM architecture). Screenshot: The above game is Labyrinth no Kanata. I've also tested it with Time Travelers, The Legend of Zelda: Ocarina of Time 3D, and Star Fox 64 3DS. Anyway, I just wanted to make everyone who could make use of it here aware that the feature is there and working at the moment in case it might be useful for anyone. As of two days ago, the gdbstub is in all nightly builds which can be found on the official Citra website. To enable the Gdbstub, check the "Use Gdbstub" option under the Emulation menu at any time during execution. The gdbstub can be enabled and disabled at any time. The default port is 24689 and can be modified by changing the gdbstub_port setting in the relevant ini file under user/config. Multiple gdbstubs can be run at the same time as long as they have different port numbers (such as multiple glfw and qt instances running at the same time).