#debuggers
Modern NES homebrew is pushing 8-bit hardware far beyond its original commercial limits. Advanced compilers, emulator debuggers, and modern toolchains let developers squeeze tricks out of the 6502 and PPU that 1980s teams on brutal deadlines never had the bandwidth to uncover. #retrogaming
November 16, 2026 at 7:00 AM
Mesen has spoiled me for debuggers. The ability to trace backwards was a game changer, and now I'm getting annoyed at my grubby old one-way Z80 tools.
November 15, 2026 at 7:50 AM
Wrong. We use debuggers made for the problem we are trying to debug.
November 10, 2026 at 12:30 PM
I've seen it. FireBug has been the culprit in the past. It happens when you use debuggers in test, and don't shut them off in a move to prod.
November 12, 2026 at 9:13 PM
Zero tolerance for genAI assets & design is correct and should be the standard. Not leveraging an LLM in any capacity during software engineering is wildly unreasonable.

Indie devs should not have to turn off autocomplete or become unpaid Unity debuggers because of some gen Z puritanical bullshit.
People are being completely insane about Big Walk
November 12, 2026 at 3:41 PM
We'll build our own tools with blackjack and hookers ;) (e.g. step-debuggers never were all that popular to begin with, and I guess that will be getting much worse now)
November 10, 2026 at 7:50 AM
Some odd wordpress theme problem?

emalliab.wordpress.com/2026/11/11/u…
## Using AI for Retro Computing I struggle with the growing use of AI in retro computing, which in this case essentially means using large language models (LLMs) and agentic systems for coding (“vibe coding”). It has definitely transformed the hobby, but in my view, I’m not sure it is for the better. We’re seeing new ports of games; new emulators; new simulators, diagnostic tools, debuggers. So the explosion of new things should be good right? I’m not convinced. At one level, I’ve yet to find good counters to the points raised in this article by Esther Weidauer: https://estherweidauer.com/articles/why-resist-generative-ai.html. I also agree with a lot of the points raised in this video, especially the part about tinkering taking over from music making – I’m definitely guilty of that, albeit not with AI systems as an excuse: https://www.youtube.com/watch?v=4NExTWq_wvk So given all the issues raised in the above two links about the design and incentives behind the use of AI (LLM) systems, I already have plenty of reasons to avoid the use of the technology in my own hobby. But this post is about something else that has only recently occurred to me which adds perhaps a more philosophical reason to hold out against its use in my own messing about. This post was inspired by two things I encountered recently. One was a post from someone I don’t know, but who I could see had done some amazing work in reverse engineering and retro computing, describing how they’d used a vibe-coding approach to their latest project really successfully. Unfortunately I read this and my main thought was “well if even someone like you can be convinced, then there is really is no going back”. But it turned out the post was a fake, designed as a parody of all the vibe-coded, mostly dodgy ports of games they were seeing. That made me realise how hard it is to know what is real anymore and I’m now naturally suspicious of any new project I read about. My interest drops off rapidly if I get to a point where it says “so I used AI for…”. The other was a video from someone I follow and respect the views of. They freely admit that they are not a coder, but was trying it out. There is a new tool they really wanted to use, but that didn’t quite do all the things they wanted. The video was a really good walk through of both the issues of vibe coding something like this alongside analysing the results. It was whilst watching this video that the essence of this blog post finally occurred to me. I’ve always been fascinated with technology so the first time I’d heard that someone had built a generative system that could use a discriminator to feedback into a generator to create a generative adversarial network (GAN), I was definitely fascinated with where “AI” was going. In truth I was reminded of Douglas Adams description of the creation of the infinite improbability drive: > _The Infinite Improbability Drive is a wonderful new method of crossing vast interstellar distances in a mere nothingth of a second, without all that tedious mucking about in hyperspace._ > > _It was discovered by a lucky chance, and then developed into a governable form of propulsion by the Galactic Government’t research team on Damogran._ > > _This, briefly, is the story of its discovery._ > > _The principle of generating small amounts of finite improbability by simply hooking the logic circuits of a Bambleweeny 57 Sub-Meson Brain to an atomic vector plotter suspended in a strong Brownian Motion producer (say a nice hot cup of tea) were of course well understood—and such generators were often used to break the ice at parties by making all the molecules in the hostess’s undergarments leap simultaneously one foot to the left, in accordance with the Theory of Indeterminacy._ > > _Many respectable physicists said that they weren’t going to stand for this, partly because it was a debasement of science, but mostly because they didn’t get invited to those sorts of parties._ > > _Another thing they couldn’t stand was the perpetual failure they encountered in trying to construct a machine which could generate the infinite improbability field needed to flip a spaceship across the mind-paralyzing distances between the farthest stars, and in the end they grumpily announced that such a machine was virtually impossible._ > > _Then, one day, a student who had been left to sweep up the lab after a particularly unsuccessful party found himself reasoning this way:_ > > _If, he thought to himself, such a machine is a virtual impossibility, then it must logically be a finite improbability. So all I have to do in order to make one is to work out exactly how improbable it is, feed that figure into the finite improbability generator, give it a fresh cup of really hot tea…and turn it on!_ > > _He did this, and was rather startled to discover that he had managed to create the long-sought-after golden Infinite Improbability generator out of thin air._ > > _It startled him even more when just after he was awarded the Galactic Institute’s Prize for Extreme Cleverness he got lynched by a rampaging mob of respectable physicists who had finally realized that the one thing they really couldn’t stand was a smart-ass._ – Douglas Adams, “The Hitchhikers Guide to the Galaxy”. This wasn’t my first encounter with generative approaches. I remember when “evolutionary computing” was a thing a few decades back and reading about a chip design that had used a system with a physics model in an evolutionary manner to design a chip. The chip worked fine. Some parts seemed to be unused and unconnected to anything, but they found that if they removed them from the design, the thing stopped working. It really had used the physics model to the full including building in emerging properties from unused parts of the device. I wonder if Terry Pratchett knew of this when he wrote about his computing engine “Hex” not working when someone took away its teddy bear… So naturally when generative pre-trained transformers (the GPT that people are now familiar with) entered the scene, again I considered it a really interesting development. Even today I still marvel that such a “brute force” approach can yield such compelling results. The technology is, as I say, quite astonishing. But I recently encountered this comment in a book from 1981 looking 100 years ahead: _“ I believe that direct communication by speech with computers will be achieved, probably within this century, but it will be possible only because computers can calculate far faster than the human brain. They will achieve their goal by methods that are really very inefficient, rather like cooking dinner by setting the house on fire.”_ – “2081: A Hopeful View of the Human Future” – Gerald O’Neill That started the wheels turning and then after watched the aforementioned video, the reasons for why I’m not a fan of their use in retro computing started to finally form. Returning to 1980s 8-bit computers reminds me of a time when technical scarcity gave constraints that led to an absolute abundance of human ingenuity. People were doing things with these small and cheap machines that seemed completely beyond their capabilities and I’m sure were never imagined by the machines’ designers and developers. There are so many examples, but I’ll point to a few here: * Turn to any chapter of “Racing the Beam” by Ian Bogost and Nick Montfort to read about the techniques developed to get, well, pretty much anything, out of an Atari 2600. So many clever people doing clever, ground-breaking, things. * My own (ongoing) analysis of the AY sound driver by Ste Ruddy written for use by Tim Follin. It is brilliant what these folk were able to do with those devices. * Michael Martin’s brilliant series of articles on the ZX Spectrum’s “1-bit sound”. Again what can be achieved from just turning the speaker on and off was amazing. * Any of Dean Belfield’s articles on tips and techniques on programming for the ZX Spectrum. * And so many more… It was this attitude of “squeeze what we can, and then a bit more” from these systems that I really value. The constraints led to a plethora of creativity and it is hard to look at some of those early 8-bit games alongside those that came later and imagine they were running on the same machine and it is great that many of these techniques are now coming out in forms that anyone can read about. And it hasn’t stopped today. With the advent of the Spectrum Next (I’ll hopefully be getting mine any day now) we can see how that ingenuity has lived on. I can’t wait to see what people are doing with them today. My interest in being optimal with computing capabilities isn’t just about older computers. Moving into more traditional modern computing communities, I look at something like the Raspberry Pi and its complete environment to get people up and running with it as a computer. And then I look at what Rene Stange did with his excellent bare-metal circle environment to allow full use of the capabilities of the hardware without those OS layers. Then I look at something like Circuitpython and Micropython and marvel at the accessibility of hardware IO in a high level-language like python on a microcontroller. But fundamentally I also can’t bring myself to use them and add those additional processing layers into the system, when I could fire up the Arduino environment and progam directly in C and do so much more. If I step back and look at the incredible range of emulation options for a retro systems from CPUs, like the Z80, to peripherals, like the ULA in the ZX spectrum and AY chips, to entire systems, like Dexed for the DX7 synthesizer. What I value in all these things is the dedicated, human ingenuity that was determined to understand how these things worked, even to the point of ensuring undocumented features were accurate and then going on to make something able to reproduce it. And this is why I think the comment from the 1981 book of “cooking the dinner by setting the house on fire” rings so true for me. Using these huge, resource intensive, brute-force methods of creation (that incidentally may or may not be “setting the world on fire”) really is the antithesis of what retro computing means to me. So even with the many reasons to already be concerned about the current incarnation of “AI” systems: from environmental impact, through cognitive debt, through building dependance (it is not “democratising programming” if it is building dependance on a paid subscription to a small number of companies), through exploitation of human creativity in their training, through addictive and gambling-like behaviours by design… … fundamentally these current systems work totally against the ethos of what I believe drove the creation the home computer market in the first place – i.e. genuinely wanting to get a wholly owned, fully-understandable, “open box”, cheap, system into the hands of those determined to poke its constraints further than believed possible to see what it can be pushed to do. I get why others are drawn to using “AI” systems. What they can do, as I say, is quite astonishing and it feels, I’m sure, quite liberating for someone to be able to produce something beyond their own skill sets or patience. I do wonder quite how many will ever see a “version 2”, but more worryingly, who is likely to work on something through that aforementioned passion to learn, when there are so many half-built versions out there flooding the scene? For me, as a technology “AI” appears to be at the polar opposite end of the, er, spectrum, to what I value about retro computing, hence “AI” is not for me. At least, not in its current form. There may be future evolutions without some of the issues. We shall see. It goes without saying, I hope, that general purpose computing has come on a long way and of course I’m not advocating a return to the unconnected days of writing using The Quill and thermal printers, or DOS and Word Perfect (although that remains, in my view, still the best word processor I’ve used during my career). Music production is of course unrecognisable to anyone from those 8-bit days. But it is also instructive to ponder the size of the average piece of Javascript that your browser downloads to support someone else’s advertising goals. And right now, just a few of the icons on this instance of WordPress I’m using to write this post, would be close to the total memory available to me in a computer whilst growing up. We do appear to waste our computing resources without a thought. I still remain fascinated by “AI” in a more general sense. I have to admit I am getting quite a lot from reading this book at the moment: Maybe that is the true way of the future – a return to basics and really learning how to get the most out of what we have, be that an 8-bit CPU, a microcontroller or the latest high spec, multi-core, multi-GHz CPU and GPU, or the growing cloud resources available on demand. But in conclusion yes, as of right now, I’m not a fan of the use of “AI” in retro computing. Kevin #ai #retro #RetroComputing #vibeCoding
emalliab.wordpress.com
November 17, 2026 at 7:41 PM
some people really love to work on dev tools/profilers/compilers/debuggers. i'm not built for that and it would melt my brain. but i'm always going to be grateful that those devs are out there writing and designing them. i don't want their sense of fulfillment to be washed away.
November 10, 2026 at 8:26 PM
Yeah graphical debuggers is just one part of the equation, the other part is that the software industry needs to reckon with the toxicity that it has festered making it shameful to ask for help, and the people who see software engineering as a dick measuring contest where they don't share knowhow
November 10, 2026 at 11:48 AM
I mean, I have been in the situation of spending weeks fighting a graphical bug and the graphical debuggers nor even contacting the platform's dev support not being able to render any solutions. Not that I think we would have found one by asking AI.
November 10, 2026 at 11:45 AM
We had an entire site for just humans sharing human knowledge about it for years, called stackoverflow. Programmers used this site to both ask questions, and share their own knowledge in the pursuit of community learning and growth. When you actually get down into it, there's also debuggers that
November 10, 2026 at 3:00 PM
One launch a year isn’t a cadence, it’s an anniversary. Distribution tip: ship publicly before you’re ready—your first users are your debuggers.
November 11, 2026 at 5:56 AM
I don't think letting AI write boilerplate is bad as long as you keep it on a short leash, and using AI debuggers is *good* because most of debugging is just finding the bad logic and pattern recognition is AI's core competency. And for research, it's just a semantic search engine, with summaries
November 10, 2026 at 1:03 PM
That's how Final Fantasy I to XII had been made, lots of backtracking and redoing.

But smaller teams in one room and debuggers who are also writers and in-game artists was much more affordable in Famicom to PS2 era. PS3 3D was way more expensive to do things as they had always done.
November 9, 2026 at 2:33 AM
Airbnb’s lesson: your first users are your best debuggers, not your first investors.
November 7, 2026 at 1:00 AM
Debugging Workflow 🐛

Identify the issue → Reproduce → Investigate → Fix → Test → Verify.

Follow a structured process to find root causes and write more reliable code.

#CodesByAbhay #AbhaySingh #Debugging #Programming #SoftwareDevelopment
November 10, 2026 at 12:21 PM
🐧 **23 Best Free and Open Source Linux Debuggers**

Debugging is the process of removing bugs. We recommend our favorite debuggers.

📰 Source: LinuxLinks
🔗 Link: https://www.linuxlinks.com/debuggers/

#linux #opensource
23 Best Free and Open Source Linux Debuggers
Debugging is the process of removing bugs. We recommend our favorite debuggers. The post 23 Best Free and Open Source Linux Debuggers appeared first on LinuxLinks.
www.linuxlinks.com
November 3, 2026 at 12:24 PM
Trace tables beat staring at debuggers—I once mapped a 200-line script’s variable states in one pass and found a typo that cost me an hour.
November 2, 2026 at 10:20 PM
🐧 **23 Best Free and Open Source Linux Debuggers**

Debugging is the process of removing bugs. We recommend our favorite debuggers.

📰 Source: LinuxLinks
🔗 Link: https://www.linuxlinks.com/debuggers/

#linux #opensource
23 Best Free and Open Source Linux Debuggers
Debugging is an essential part of software development. When a program crashes, behaves unexpectedly or produces incorrect results, a debugger can help identify the cause. Developers can pause execution, step through code and inspect variables, memory and the call stack. Linux offers a wide range of debugging tools. These include source-level debuggers, graphical frontends, language-specific debuggers and utilities for examining compiled binaries. Memory analysis and tracing tools can also help uncover problems that are difficult to reproduce. Some debuggers concentrate on everyday programming tasks, while others specialise in reverse engineering, low-level analysis or investigating problems in running processes. Our selection covers these different approaches. Bug tracking software are covered in our **Issue Tracking roundup**. A memory debugger is a programming tool for finding memory leaks and buffer overflows. These are due to bugs related to the allocation and deallocation of dynamic memory. Programs written in languages that have garbage collection, such as managed code, might also need memory debuggers. Here’s a legendary LinuxLinks-style ratings chart capturing our recommendations. All of the software featured here are free and open source goodness. Click the links in the table to learn more about each debugger. **Debuggers** --- **LLDB**| Next generation, high-performance debugger **Ghidra**| Software reverse engineering framework **Delve**| Source level debugger for the Go programming language **GDB**| The GNU Debugger **Valgrind**| A memory debugger and profiler **Radare2**| Portable reversing framework **BugStalker**| Rust debugger **Xdebug**| Extension for PHP to aid debugging and development **Seer**| GUI frontend to GDB **iaito**| Graphical interface for radare2 **KDbg**| Graphical user interface to GDB **strace**| Diagnostic, debugging and instructional userspace utility **rr**| Record-and-replay debugger **gf**| Lightweight GDB interface with source, stack and memory views **drgn**| Programmable debugger that puts scripting at the centre **cgdb**| Lightweight console frontend to the GNU debugger **PuDB**| Console-based visual debugger for Python **nnd**| Partially inspired by RemedyBG **bashdb**| Source-code debugger for bash; follows the GDB command syntax **PINCE**| Memory scanning, process manipulation and reverse engineering **edb**| Low-level debugging with disassembly and register inspection **Sysprof**| Profile an application or entire system **crash**| Linux kernel crash analysis utility This article has been updated to reflect the changes outlined in our **recent announcement**. LinuxLinks helps you discover the best free and open source software for Linux. Explore our extensive collection of **recommended applications** , including alternatives to popular proprietary software. We also publish software reviews, Linux tutorials, hardware reviews, free programming books and articles covering the wider open source community. Browse our **Linux resources** to discover more. Know a useful free and open source Linux application we haven't covered? **Suggest a program** for inclusion. Has your software been featured on LinuxLinks? Display one of our **Featured on LinuxLinks badges** on your website or GitHub README. ---
www.linuxlinks.com
November 1, 2026 at 12:18 PM
I have urged the husband to tattle on this little criminal's PLASTIC EATING CRIMES in case he forgot to mention it to the cat debuggers

Here is is not getting triaged to the top of the pile bc it's a pet ER and he is not bleeding

Husband says his tail be thrashing
October 31, 2026 at 5:47 PM
I gave Claude Code debuggers via a session-manager daemon I made and it absolutely loves it
October 27, 2026 at 6:06 AM