eupolicy.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
This Mastodon server is a friendly and respectful discussion space for people working in areas related to EU policy. When you request to create an account, please tell us something about you.

Server stats:

196
active users

#debugging

5 posts5 participants1 post today

Grr. ok with openocd I can probe the NAND over jtag, and see the info....

> nand probe 0
NAND flash device 'NAND 256MiB 3.3V 8-bit (Hynix)' found

> nand info 0 0 1
#0: NAND 256MiB 3.3V 8-bit (Hynix) pagesize: 2048, buswidth: 8, erasesize: 131072
#0: 0x00000000 (128kB) erase state unknown (block condition unknown)
#1: 0x00020000 (128kB) erase state unknown (block condition unknown)

but I can't read/dump. ☹️
> nand dump 0 test.dump 0x20000 0x800
reading NAND flash page failed

Not sure what could be wrong/need changing. 😡 This is driving me mad, although I'm not an openocd expert to know why the info would work but read not.

Continued thread

Ah, and also, forgot to mention this change:

Improved:

• Debugging your Kitten app is now easier when you run it using `INSPECT=true kitten …` as the Node runtime is launched using the `--inspect-brk` tag instead of the `--inspect` tag. This means that execution will wait for your debugger (e.g., Chromium’s DevTools at `chrome://inspect`, etc.) to connect before starting the server. This makes it possible to hit breakpoints that might previously have been impossible to reach as they occured before you had a chance to run the debugger.

Full change log:
codeberg.org/kitten/app/src/br

Summary card of repository kitten/app
Codeberg.orgapp/CHANGELOG.md at mainapp - A web development kit that’s small, purrs, and loves you.

Aha, re-entry bug in @disaster_bot -- I was throwing evacuations into that bot and there were two dozen evac zones triggered in Yreka, which took longer to draw than the 4 minute update. So it started again, and started drawing the zones (again)... repeat until OOM crash (no crash, caught it). Properly forced the code to lock before execution, and timeout if it cannot receive the lock. #software #debugging

Do AI models help produce verified bug fixes?

"Abstract: Among areas of software engineering where AI techniques — particularly, Large Language Models — seem poised to yield dramatic improvements, an attractive candidate is Automatic Program Repair (APR), the production of satisfactory corrections to software bugs. Does this expectation materialize in practice? How do we find out, making sure that proposed corrections actually work? If programmers have access to LLMs, how do they actually use them to complement their own skills?

To answer these questions, we took advantage of the availability of a program-proving environment, which formally determines the correctness of proposed fixes, to conduct a study of program debugging with two randomly assigned groups of programmers, one with access to LLMs and the other without, both validating their answers through the proof tools. The methodology relied on a division into general research questions (Goals in the GoalQuery-Metric approach), specific elements admitting specific answers (Queries), and measurements supporting these answers (Metrics). While applied so far to a limited sample size, the results are a first step towards delineating a proper role for AI and LLMs in providing guaranteed-correct fixes to program bugs.

These results caused surprise as compared to what one might expect from the use of AI for debugging and APR. The contributions also include: a detailed methodology for experiments in the use of LLMs for debugging, which other projects can reuse; a finegrain analysis of programmer behavior, made possible by the use of full-session recording; a definition of patterns of use of LLMs, with 7 distinct categories; and validated advice for getting the best of LLMs for debugging and Automatic Program Repair"

arxiv.org/abs/2507.15822

arXiv.orgDo AI models help produce verified bug fixes?Among areas of software engineering where AI techniques -- particularly, Large Language Models -- seem poised to yield dramatic improvements, an attractive candidate is Automatic Program Repair (APR), the production of satisfactory corrections to software bugs. Does this expectation materialize in practice? How do we find out, making sure that proposed corrections actually work? If programmers have access to LLMs, how do they actually use them to complement their own skills? To answer these questions, we took advantage of the availability of a program-proving environment, which formally determines the correctness of proposed fixes, to conduct a study of program debugging with two randomly assigned groups of programmers, one with access to LLMs and the other without, both validating their answers through the proof tools. The methodology relied on a division into general research questions (Goals in the Goal-Query-Metric approach), specific elements admitting specific answers (Queries), and measurements supporting these answers (Metrics). While applied so far to a limited sample size, the results are a first step towards delineating a proper role for AI and LLMs in providing guaranteed-correct fixes to program bugs. These results caused surprise as compared to what one might expect from the use of AI for debugging and APR. The contributions also include: a detailed methodology for experiments in the use of LLMs for debugging, which other projects can reuse; a fine-grain analysis of programmer behavior, made possible by the use of full-session recording; a definition of patterns of use of LLMs, with 7 distinct categories; and validated advice for getting the best of LLMs for debugging and Automatic Program Repair.

🐍 Decode Any Python Code With This 5-Step Method

「 It’s rare to write all the original code in an application yourself, and even rarer for an application to be completely rewritten from scratch. More likely, your workflow will involve working with code that was written by someone else (who may no longer be available to explain it) and iterated on by others (who also might be out of reach) long before it ever appears on your screen 」

thenewstack.io/decode-any-pyth

The New Stack · Decode Any Python Code With This 5-Step MethodMaster the skill of reading and understanding messy, poorly documented code written by others using a simple checklist that transforms confusing scripts into clear programs.

🥳 Xdebug 3.4.5 Released!

🐛 This is a bug fix release.

🧬 One fix addresses crashes when using Xdebug's debugger with (nested) Fibers.

↪️ A second bug addresses an issue where, while debugging, Xdebug sometimes calls get property hooks which can then update and change the object's state.

📄 The full list of changes can be found on the updates page: xdebug.org/announcements/2025-

xdebug.orgXdebug - Xdebug 3.4.5 is out!Xdebug: A powerful debugger for PHP

We are happy to announce the first stable release V1.0.0 of bmputil! This Black Magic Probe Utility simplifies the process of keeping your Black Magic Probe configured and up to date. The main new feature is the ability to automatically find and download the newest Black Magic Probe firmware. No need to find binaries any more! Massive thanks to @dragonmux for a big push to make this release a reality! #opensource #rust #embedded #jtag #swd #debugging #mcu #electronics github.com/blackmagic-debug/bm

Replied in thread

So after figuring out which bits to remove, I set about building it. I first tried laying it out on a single one of my custom #protoboards I posted about before. It gets very dense, and would require cutting / splitting a whole lot more of the 6-hole #pad #strips than I really wanted to do. So I built it on two boards, using the same modular connection between them that I use for the rest of my effects boards.

Even the original Boss pedal used 2 separate boards, so I don't feel too badly about it.

Anyway... it took a while to fiddle with the layouts to get something I like, then document my parts placement, remove all the parts and start re-populating and #soldering them into place. But I got that done this evening.

I did a little meter #probing of the results to find any obvious missing connections or such, and fixed a couple. Then I plugged in my guitar, and ...

It #worked, perfectly, the first time. I believe that's the first time any of my effects have not required any #debugging at all. I'm #chuffed .

And it sounds *fantastic*.

The originally-called-for #transistors and #diodes are mostly #obsolete and hard to find. I dug through datasheets to find ones I thought would (a) be acceptable substitutes, and (b) I already had in my parts bins. Frankly, given the nature of the effect, I doubt the selections are too critical, but I'll include what I used for completeness, in case anyone else wants to make one of these.

#maker #components #substitute

4/x