Fuck me! I tried to upgrade tview and the first thing I notice is a shitload of added dependency versions:

go.mod | 18 ++++-----
go.sum | 97 ++++++++++++++++++++++++++++++++++++++-----------

My code does not compile anymore as the view.FormItem interface was extended. Get/SetDisabled(…) are quickly implemented, no worries.

But the tview.Primitive (what makes a widget) interface has now a bunch of PRIVATE methods. For focus handling. Would you believe that!? Thanks, I cannot satisfy this interface in my very custom widgets anymore. Okay then, I just embed *tview.Box. tt now successfully compiles, but does not react anymore on key presses and the message tree is not focused either.

I’m not in the mood to debug this shit. :-( Lunch time.

The LD_DEBUG environment variable (2012)
Article URL: https://bnikolic.co.uk/blog/linux-ld-debug.html

Comments URL: https://news.ycombinator.com/item?id=48464330

Points: 3

# Comments: 0 ⌘ Read more

Google Requests Permission to Release 32 Million Mosquitoes In California and Florida
Google has asked the EPA for permission to release up to 32 million sterile male mosquitoes in California and Florida over two years. The effort is part of the company’s Debug program, which uses Wolbachia-infected males to reduce populations of disease-spreading Aedes aegypti mosquitoes. Google cites a si … ⌘ Read more

Debug Project
Article URL: https://debug.com/

Comments URL: https://news.ycombinator.com/item?id=48362347

Points: 3

# Comments: 0 ⌘ Read more

On the subject of debugging these so-called AI(s) / Black Boxes… the model is a black box sure, but that’s not really the problem. Everything around it — the inputs, the outputs, the decisions it makes — all of that can and should be fully logged, traced and replayed. The “program” isn’t the model, it’s the full context you feed it. That’s what you debug. It’s not so different from any other system really; if you’re running something in production with no logs, no structured outputs and no tests, you’d have the same problem. The model doesn’t change that discipline, it just makes it more important.

@prologic@twtxt.net

it’s “probabilistic” not “deterministic”

Yep, I know. And when I tell that to people and tell them “if we use AI here, we lose the ability to debug this stuff”, then all I get is: “But it’s good enough. We don’t need to debug this. Non-deterministic computing has its use cases.”

But that is just not how I’d like to model/implement our business processes. 🤔 I want something reliable, not “it mostly works”.

@prologic@twtxt.net Ahh, I see. Okay, I’m with you there. On this high level, I can understand how the thing works.

Maybe my wording isn’t good. 🤔 Let’s take a real life example from what we do at work.

There’s this AI chatbot. It gets support requests from users, so the user says something like “I need access to a particular system”. This triggers the bot to “run” the instructions stored in a large Markdown file, like “check if the user is authorized to do this, then issue the following API requests”, and so on. This is essentially like running a little script, except it’s written in natural language (German) and there’s no “script interpreter” but just the AI.

Now, suppose that the AI doesn’t quite do what was intended. There’s some subtle bug. How do you debug this? How do you find out how the AI came to the “conclusion” to run step A instead of step B? And how do you find out how exactly you have to change your prompt so this doesn’t happen again next time?

If this was an actual script/program instead of AI, you could repeat the request and attach a debugger or throw in some printf() or whatever. How do you do that kind of thing with AI? How do you pinpoint exactly what the problem was?

(Or is this just a stupid idea? Do we have to give up that way of thinking when using AI? Is the era of debuggability over?)

@lyse@lyse.isobeef.org Yeah, that was an interesting debugging session. :-) (Those have become rare, lately …)

OpenAI Says Its New GPT-5.5 Model Is More Efficient and Better At Coding
OpenAI released its new GPT-5.5 model today, which the company calls its “smartest and most intuitive to use model yet, and the next step toward a new way of getting work done on a computer.” The Verge reports: OpenAI just released GPT-5.4 last month, but says that the new GPT-5.5 “excels” at tasks like writing and debugging code, doing … ⌘ Read more

Another AI rant:

One of the “key features” of LLMs is that you can use “natural language”, because that is supposed to be easier than having to learn a programming language. So, when someone says to me, “I automated this process using AI!”, what they mean is: They have written a very, very large Markdown document. In this document, they list what the AI is supposed to do.

In prose.

This is a complete disaster.

Programming and programming languages have one crucial property: They follow a well-defined structure and every word has a well-defined meaning. That is absolutely brilliant, because I can read this and I can follow the program in my head. I can build a mental model. I can debug this, down to the precise instructions that the CPU executes. This all follows well-defined patterns that you can reason about.

But with these Markdown files, I am completely lost. We lose all these important properties! No debugging, no reasoning about program flow, nothing. It’s all gone. It’s a magic black box now, literally randomized, that may or may not do what you wanted, in some order.

People now throw these Markdown files at me … and … am I supposed to read this? Why? It’s completely random and fuzzy.

Sadly, these AI tools are good enough to be able to mostly grasp the authors intentions. Hence people don’t see the harm they cause, because “it works”.

We already have a ton of automations like this at work: Tickets get piped through an LLM and these Markdown files / prompts determine what will happen with the ticket, and maybe they trigger additional actions as well, like account creation or granting permissions. All based on fuzzy natural language – that no two humans will ever properly agree on.

Jesus Christ, we’re now INTENTIONALLY bringing the ambiguity of legal texts and lawyers into programming.

Using natural language is NOT easier than using a programming language. It is HARDER. Have you people never read a legal contract? And that stuff can STILL be debated in a court room.

I can’t begin to comprehend why we, tech folks, push this so hard. What is wrong with you? Or me?

(And, once again, we’re ignoring other factors here. LLMs use a ton of energy and ressources, that we don’t have to spare. It’s expensive as fuck. It doesn’t even run locally on our servers, meaning we give all these credentials and permissions to some US company. It’s insane.)

A Small But Useful Debugging Addition For AMD Zen Systems With Linux 7.1
A small but convenient feature is coming with the Linux 7.1 that will be useful in debugging AMD Zen system problems and information reporting/transparency purposes… ⌘ Read more

AMDGPU Driver For Linux 7.1 Preps Debug Improvements, New Hardware IP
Another round of AMDGPU/AMDKFD kernel driver improvements were sent out this week as feature development for DRM-Next ahead of Linux 7.1 begins to wind down… ⌘ Read more

@lyse@lyse.isobeef.org Changing the user name helped, it now says Authenticated to git.mills.io ([199.247.16.95]:2222) using "publickey". ssh-add ... had no effect (even after ssh-add -D).

Here’s a debug log, @prologic@twtxt.net, perhaps you could take a look at this 🙏: https://movq.de/v/116c5f514b/clone2.txt

(Might be a silly mistake on my part. Wrong remote path or something?)

AMD Engineer Leverages AI To Help Make A Pure-Python AMD GPU User-Space Driver
AMD’s VP of AI Software, Anush Elangovan, has used Claude Code to help craft a pure-Python AMD GPU user-space driver. This Python user-space driver is currently being created to help exercise other ROCm code and for debugging in passing through the ROCm/HIP user-space stack… ⌘ Read more

Weird. My timestamps are all being shown (on https://twtxt.net and https://darch.dk/timeline) one hour ahead of what I expected. Am I manually writing my timestamps wrong? Are the clients interpreting something I’m not aware of? Let me write this one on the “Z” timezone to try to debug it.

AI Helped Uncover A “50-80x Improvement” For Linux’s IO_uring
Linux block maintainer and IO_uring lead developer Jens Axboe recently was debugging some slowdowns in the AHCI/SCSI code with IO_uring usage. When turning to Claude AI to help in sorting through the issue, patches were devised that can deliver up to a “literally yield a 50-80x improvement on the io_uring side for idle systems.” The code is on its way to the Linux kernel… ⌘ Read more

Mesa Will Now Prevent Compiling With LTO Due To “Random Impossible-To-Debug Bugs”
While link-time optimizations “LTO” can deliver some nice performance benefits out of this compiler optimization technique, it can make debugging said binaries more challenging. Due to various bugs in Mesa being attributed to the use of compiler link-time optimizations when compiling Mesa, the builds are being blocked on using LTO… ⌘ Read more

Here am I looking at the different tcell.Key constants and typing different key combinations in the terminal to see the generated tcell.EventKeys in the debug log. Until I pressed Ctrl+Alt+Backspace… :-D Yep, suddenly there went my X…

So far, it appears as if I can have either only Ctrl or Alt as modifiers. But not in combination. And Shift is just never ever set at all. Interesting.

@prologic@twtxt.net Debugging this stuff on bare metal hardware (without an underlying OS) is a nightmare. 🤣

@lyse@lyse.isobeef.org I can tell you this right now, writing assembly / machine code is fucking hard work™ 😓 I’m sure @movq@www.uninformativ.de can affirm 🤣 And when it all goes to shit™ (which it does often), man is debugging fucking hard as hell! Without debug symbols I can’t use the regular tools like lldb or gdb 😂

GNU Debugger 17.1 Released With CET Shadow Stack Support, New DAP Features
The GNU Debugger “GDB” 17.1 is out today with a number of new features for enhancing the open-source debugging experience… ⌘ Read more

Intel’s Vulkan Linux Driver Merges Shader VMA Allocator For Ray-Tracing Capture/Replay
Merged today to the Intel open-source “ANV” Vulkan driver in Mesa 26.0 is introducing a shader VMA allocator. Long story short this new allocator steps toward enabling Vulkan ray-tracing capture/replay support, which can come in hand for debugging issues with Vulkan ray-tracing on Intel graphics hardware under Linux and similarly to assist in optimizing for better performance… ⌘ Read more

Claude Code Is Coming To Slack
Anthropic is bringing Claude Code directly into Slack, letting developers spin up coding sessions from chat threads and automate workflows without leaving the app. TechCrunch reports: Previously, developers could only get lightweight coding help via Claude in Slack – like writing snippets, debugging, and explanations. Now they can tag @Claude to spin up a complete coding session using Slack context like bu … ⌘ Read more

Anthropic Acquires Bun In First Acquisition
Anthropic has made its first acquisition by buying Bun, the engine behind its fast-growing Claude Code agent. The move strengthens Anthropic’s push into enterprise developer tooling as it scales Claude Code with major backers like Microsoft, Nvidia, Amazon, and Google. Adweek reports: Claude Code is a coding agent that lets developers write, debug and interpret code through natural … ⌘ Read more

When the architect quickly explains how the project is built so I can debug it ⌘ Read more

MEMINSPECT Proposed For The Linux Kernel To Help In Memory Analysis / Debugging
A patch series sent out today on the Linux kernel mailing list proposes “MEMINSPECT” as a new mechanism for helping with memory analysis… ⌘ Read more

Docker Desktop 4.50: Indispensable for Daily Development
Docker Desktop 4.50 represents a major leap forward in how development teams build, secure, and ship software. Across the last several releases, we’ve delivered meaningful improvements that directly address the challenges you face every day: faster debugging workflows, enterprise-grade security controls that don’t get in your way, and seamless AI integration that makes modern development… ⌘ Read more

Debugging BeagleBoard USB boot with a sniffer: fixing omap_loader on modern PCs
Comments ⌘ Read more

Debugging BeagleBoard USB boot with a sniffer: fixing omap_loader on modern PCs
Comments ⌘ Read more

When I have to debug a colleague’s code from 2019 ⌘ Read more

GitHub Copilot tutorial: How to build, test, review, and ship code faster (with real prompts)
How GitHub Copilot works today—including mission control—and how to get the most out of it. Here’s what you need to know.

The post [GitHub Copilot tutorial: How to build, test, review, and ship code faster (with real prompts)](https://github.blog/ai-and-ml/github-copilot/a-developers-guide-to-writing-debugging-reviewing-and-shipping-co … ⌘ Read more

Claude Code Can Debug Low-level Cryptography
Comments ⌘ Read more

The Owl, The Scientific Method, and Claude Code: A Debugging Story
Comments ⌘ Read more

When I fall into a loop that does nothing while debugging step by step ⌘ Read more

Adding distributed tracing to AI Gateway: My LFX mentorship journey
In today’s rapidly evolving AI landscape, effectively monitoring and debugging AI Gateways has become a critical challenge. This article shares my complete experience through the LFX Mentorship program, where I added OpenTelemetry distributed tracing support to… ⌘ Read more

Debug Docker Builds with Visual Studio Code
Building Docker images is an important component of the software delivery pipeline for modern applications. It’s how we package our apps and services so that they can be distributed to others and deployed to production. While the Dockerfile has long been the standard for defining container images, it is known to be challenging to make… ⌘ Read more

Colored Highlighter - A terminal tool to highlight specific words in your command output with colors
I needed to take a look at some live logs and quickly analyze some old ones, but I couldn’t find anything effective to highlight terms, except for esoteric sed and awk commands.
So I built ch - Colored Highlighter - a simple terminal tool to highlight specific words in your command output with colors. Perfect for tailing logs, debugging, and making command output more readable.

Try it out, all feedback is welcome!

[Comments](https://l … ⌘ Read more

Debugging a Go runtime crash: the one-instruction window
Comments ⌘ Read more

It happened.

“Can you help me debug this program? I vibe coded it and I have no idea what’s going on. I had no choice – learning this new language and frameworks would have taken ages, and I have severe time constraints.”

Did I say “no”? Of course not, I’m a “nice guy”. So I’m at fault as well, because I endorsed this whole thing. The other guy is also guilty, because he didn’t communicate clearly to his boss what can be done and how much time it takes. And the boss and his bosses are guilty a lot, because they’re all pushing for “AI”.

The end result is garbage software.

This particular project is still relatively small, so it might be okay at the moment. But normalizing this will yield nothing but garbage. And actually, especially if this small project works out fine, this contributes to the shittiness because management will interpret this as “hey, AI works”, so they will keep asking for it in future projects.

How utterly frustrating. This is not what I want to do every day from now on.

Auditing user activity in pods and nodes with the Security-Profiles-Operator
Kubernetes’ native audit logs are essential for tracking control plane activities, but they fail to capture what happens inside a container or on the host node itself during kubectl debugging sessions. This creates a security and… ⌘ Read more

CodeQL zero to hero part 5: Debugging queries
Learn to debug and fix your CodeQL queries.

The post CodeQL zero to hero part 5: Debugging queries appeared first on The GitHub Blog. ⌘ Read more

Task for this weekend:

https://movq.de/v/b05a7ce782/vid-1758959332.mp4

When you call man ascii, you get this nice table, but there’s a weird vertical line at the bottom. That line is supposed to be a vertical rule and is supposed to go from the bottom of the table all the way to the top.

Let’s see if I can debug this. (Not getting my hopes up at this point, but I’ll try.)

ESP32 Bus Pirate Turns Low-Cost Boards into Multi-Protocol Debugging Tools
An open-source project called ESP32 Bus Pirate has been released, inspired by the classic Bus Pirate and adapted for modern ESP32-S3 hardware. Developed by Geo-tp, the firmware transforms low-cost ESP32 boards into versatile debugging devices that can probe, sniff, and interact with a wide range of digital and radio protocols. The firmware supports protocols such […] ⌘ Read more

@zvava@twtxt.net Going to have to hard disagree here I’m sorry. a) no-one reads the raw/plain twtxt.txt files, the only time you do is to debug something, or have a stick beak at the comments which most clients will strip out and ignore and b) I’m sorry you’ve completely lost me! I’m old enough to pre-date before Linux became popular, so I’m not sure what UNIX principles you think are being broken or violated by having a Twt Subject (Subject) whose contents is a cryptographic content-addressable hash of the “thing”™ you’re replying to and forming a chain of other replies (a thread).

I’m sorry, but the simplest thing to do is to make the smallest number of changes to the Spec as possible and all agree on a “Magic Date” for which our clients use the modified function(s).

@movq@www.uninformativ.de Woah, cool!

(WTF, asciiworld-sat-track somehow broke, but I have not changed any of the scripts at all. O_o It doesn’t find the asciiworld-sat-calc anymore. How in the world!? When I use an absolute path, the .tle is empty and I get a parsing error. Gotta debug this.)

@zvava@twtxt.net I was about to suggest that you post some examples. By now, we’re pretty good at debugging hashing issues, because that happens so often. 😂 But it looks like you figured it out on your own. ✌️

Since Google announced their intentions to heavily limit sideloading on Android, starting end of 2026, I’ve been looking for potential solutions, for this policy change, that threatens the majority of projects I maintain, in some way. Google already killed my browser project years ago, but I have no other choice, than to fight this, any way I can.

The best choice to deal with this, will probably be the Android Debug Bridge, which can be used not only to install apps unrestricted, but also to uninstall, or remove, almost any unnecessary part of the OS. Shizuku, combined with Canta Debloater, is the winning combination for now.

I’ve already removed most Google apps from my device: the annoying AI assistant, the stupid Google app adding the annoying articles, left of your homes screen, Google One, Gboard, Safety app… it’s amazing, no distracting Google slopware, like in the good old Android 2 days! And I absolutely intend to keep it this way, from now on, no new Google apps or services on my devices, unless Google can give me a good enough reason, to allow them there and whenever the app that verifies signatures, to block installing apps not approved by Google, I’ll just remove it from my device and advocate others do so too.

@movq@www.uninformativ.de Yikes! Debug settings enabled right from “the factory”?

(Now why is that GNOME gcr thing running with debug logs enabled that print stuff like “sending secret exchange: …”? Is this healthy?)

I did a “lecture”/“workshop” about this at work today. 16-bit DOS, real mode. 💾 Pretty cool and the audience (devs and sysadmins) seemed quite interested. 🥳

• People used the Intel docs to figure out the instruction encodings.
  
• Then they wrote a little DOS program that exits with a return code and they used uhex in DOSBox to do that. Yes, we wrote a COM file manually, no Assembler involved. (Many of them had never used DOS before.)
  
• DEBUG from FreeDOS was used to single-step through the program, showing what it does.
  
• This gets tedious rather quickly, so we switched to SVED from SvarDOS for writing the rest of the program in Assembly language. nasm worked great for us.
  
• At the end, we switched to BIOS calls instead of DOS syscalls to demonstrate that the same binary COM file works on another OS. Also a good opportunity to talk about bootloaders a little bit.
  
• (I think they even understood the basics of segmentation in the end.)
  

The 8086 / 16-bit real-mode DOS is a great platform to explain a lot of the fundamentals without having to deal with OS semantics or executable file formats.

Now that was a lot of fun. 🥳 It’s very rare that we do something like this, sadly. I love doing this kind of low-level stuff.